[AAASM-4704] 🔖 (examples): Exact-pin 4 python examples + drop stale headers

[Chisanan232]

What changed

Two small consistency fixes across the examples gallery:

(a) Exact-pin 4 python examples. crewai-research-crew,
langchain-basic-agent, custom-tool-policy and haystack-tool-policy pinned
the core SDK with a bare >=0.0.1rc5, unlike the other 14 python examples which
use exact ==. Per repo policy a bare >= floor lets a resolver drag in an
unintended newer release, so these are tightened to ==0.0.1rc5. Each uv.lock
is refreshed in lockstep (the locks were additionally stale at rc3 — the refresh
corrects that too). Only agent-assembly changed in the locks; no transitive
churn.

(b) Drop stale "(coming soon)" table headers. The python/ and scenarios/
index READMEs and the Node/Go/Scenarios tables in docs/choosing-an-example.md
still labelled their sub-project column "(coming soon)" although the examples now
exist — matching the wording the node/ and go/ index READMEs already use.
Table column widths are preserved so the tables stay aligned (verified: pipe
columns match their separator rows, and the reworded headers now read identically
to the already-clean python header in choosing-an-example.md).

Out of scope (left untouched): the genuinely-pending "(coming soon)" in
.github/workflows/README.md and the "Coming soon" planned-structure heading in
scenarios/policy-enforcement/README.md.

Related ticket

Closes AAASM-4704

Jira: https://lightning-dust-mite.atlassian.net/browse/AAASM-4704

Stacked PR

This PR is stacked on #309 (AAASM-4703), which is stacked on #308 (AAASM-4702).
It branches from v0.0.1/AAASM-4703/readme_prereq_row; its base is master per
repo convention. Merge order: #308 → #309 → #310. The two-commit diff here is
the only delta over #309.

How to verify

python scripts/generate_example_metadata.py && git diff --exit-code   # idempotent
grep -rn '"agent-assembly>=' python/*/pyproject.toml                    # no bare >= remains
grep -c "coming soon" python/README.md scenarios/README.md docs/choosing-an-example.md  # 0/0/0

Checklist

• PR title follows [AAASM-XXXX] <GitEmoji> (<scope>): <summary>
• No secrets, API keys, or .env files committed
• Example sub-projects include their own README.md with prerequisites and run instructions
• SDK/runtime version dependencies are documented or pinned

[Chisanan232]

Review (AAASM-4704) — READY (stacked on #309; merge last).

• Scope: the 4 bare >= python pins tightened to exact ==0.0.1rc5 (uv.locks refreshed, only agent-assembly changed), and the stale "(coming soon)" headers dropped from the 3 index spots.
• Side effects: column alignment preserved; genuinely-pending "coming soon" markers (workflows README, policy-enforcement scenario) correctly left untouched. Depends on [AAASM-4702] 🐛 (examples): Cover scenario agents in bump tooling + dependabot #308 and [AAASM-4703] 🐛 (examples): Generator-own the README prerequisites SDK version #309.

---

CI: all required checks green. Front-end: no FE/dashboard code touched — Playwright validation N/A. Merge state: BLOCKED only on the required ≥1 Pioneer approval (branch protection), not on any failure.

— Reviewed by Claude Code

[Chisanan232]

Rebased onto latest master. #309 (its stack parent) merged, so this branch was rebased with --onto master to drop the already-merged parent commits and replay only its own two commits (exact-pin the 4 python examples; drop stale "(coming soon)" headers) — clean, no conflicts. Generator re-verified idempotent (generate_example_metadata.py → git diff --exit-code clean); the 4 pins confirmed ==0.0.1rc5 with no bare >= remaining, and no "coming soon" left in the 3 index spots. Now a standalone PR on master.

— Reviewed by Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud