docs: Adopt in your stack + show-hn uvx funnel (PR5)

[SollanSystems]

PR5 — Adopt in your stack + show-hn uvx funnel

Closes the adoption-slices plan by giving the four on-ramps shipped in PR1–PR4
(the self-contained wheel + uvx funnel, the loop.emit writer API, the
Stop-hook false-completion firewall, and the GitHub Action + pre-commit gate) a
single, coherent "Adopt in your stack" README section — and a test that keeps
every claim in that section honest.

Two commits

• 80a27ad — docs: Adopt in your stack (already on the branch): adds the
  README "Adopt in your stack" section + Install refresh. Leads with zero-install
  uvx loop-engineer inspect ., then the loop.emit writer for foreign runtimes,
  the Stop-hook firewall, and the CI Action / pre-commit gate.
• 7ce3938 — test(docs): adoption claims are gate-backed (this commit): the
  docs-claims gate scripts/test_docs_adoption.py + the CHANGELOG entry for this
  PR. Stages exactly those two files.

The docs-claims gate (scripts/test_docs_adoption.py)

Five tests assert every "Adopt in your stack" README claim is backed by a
shipped, wired artifact — the docs cannot advertise an on-ramp that does not
exist:

1. test_uvx_funnel_claim_is_backed_by_console_script — the uvx loop-engineer
   claim is backed by the loop-engineer = "loop.__main__:main" console script in
   pyproject.toml.
2. test_emit_claim_names_only_real_functions — every loop.emit function the
   README names (open_contract, append_iteration, append_receipt,
   terminate) is a real callable, and docs/integrations/langgraph.md exists.
3. test_stop_firewall_claim_is_backed_by_registered_hook — the Stop-hook
   firewall claim resolves to a real hook file registered in plugin.json
   (hooks/stop_firewall.py).
4. test_ci_action_claim_is_backed_by_action_and_precommit — the
   uses: SollanSystems/loop-engineer@… claim is backed by action.yml, and the
   loop-doctor mention by the id: loop-doctor pre-commit hook.
5. test_show_hn_leads_with_the_uvx_funnel — the M5-LAUNCH Show HN draft's first
   command is uvx loop-engineer inspect ..

The show-hn edit lives outside this PR

Task 13 changed roadmap/launch/.loop/artifacts/M5-LAUNCH/show-hn.md to lead with
uvx loop-engineer inspect .. roadmap/ is deliberately gitignored — the draft
is a launch working file, present locally but absent in a fresh CI checkout.
So test 5 is env-guarded: it runs the brief's assertions verbatim when the file
exists and pytest.skips (with a clear reason) when it doesn't, matching the
repo's existing env-guarded-skip pattern (wheel/recipe/pre-commit tests).

Forward-looking pins

The README's CI-Action snippet pins SollanSystems/loop-engineer@v0.7.0 and the
uvx/pip paths reference the not-yet-published PyPI project. These are
deliberate forward-looking pins for the adoption story; Task 15 re-verifies them
at release.

Expected CI skip delta

Local (draft present): 251 passed / 9 skipped, self_eval 13/13. In a fresh
CI checkout the show-hn test skips, so CI shows one more skip than local — the
same pattern the plan's Global Constraints bless. The other four tests read only
tracked files and always run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01As92NaD7jMDbnQTqXDzBVa

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.