[yia-mw-agent]

Summary

Integrates the accepted final release documentation package for MachineWisdomAI/fava-trails.org#38 into the product repository. Documentation only; no runtime, ordering or configuration change.

• README: the release boundary now says the main branch can be ahead of the installed package and that the 0.9.0rc1 walkthrough candidate was locally built and never published. The "from 0.9.0" label is gone, a second machine no longer needs its own identity, and the SECOM paragraph states the actual order.
• SECOM order (traced from tools/navigation.py and trail.py): the reviewer reads the draft as saved and returns its verdict first. Then before_propose hooks run inside the same propose_truth call, before the verdict is applied and persisted. They also run for reject and error verdicts. With the default fail_mode: open a hook error lets the promotion continue uncompressed. Setup guide S9 and S11 and README Protocols agree.
• Repairs the root setup guide link to the SECOM README (src/fava_trails/protocols/secom/README.md), and replaces a tracker label in the calibration report link text.
• CONTRIBUTING and runtime-and-upgrade: release grammar matches scripts/release-tag.py and release.yml (stable vX.Y.Z or candidate vX.Y.ZrcN, tag minus v equals the package version); merge everything intended for a release before tagging; the 0.6.0 upgrade test is described as a fixed fixture, not a supported-minimum claim; the maintainer vendor/client upgrade steps are separated from read-only feature work.
• documentation-ownership, blueprint-maintenance, local-review blueprint status line and the FAQ banner: describe the local reviewer as a source feature and name a published release only after it is verified to contain it.

Not touched: runtime code, existing MCP installations, client registrations, stored records, release history, archived FAQ body and one-pager (the FAQ banner wording only).

Version

Markdown-only change, so scripts/mw-version.py check --base origin/main reports 0.9.2-rc.1 -> 0.9.2-rc.1 (unchanged component) and passes. No tag, release or publication is made by this PR; publication follows the existing Release workflow after merge.

Verification

• All 26 package patches matched their Old strings exactly once; README replaced with the package full-file block.
• Relative links and anchors in the 9 changed Markdown files: 127 links, 0 broken (includes the repaired SECOM link and #working-in-this-repository).
• Version policy check passed.
• Full pytest run result is recorded in the PR comment below.

[yia-mw-agent]

Verification at head 348e8da (documentation-only; no runtime change):

• All 26 package patches matched their Old strings exactly once, and the README is the package full-file block. Two further one-line repairs outside the package patches, for the same stale "from 0.9.0" / "installed 0.9.0rc1" wording: the local-review blueprint status line and the FAQ banner.
• Full local pytest run: 1230 passed, 3 failed. The three failures are tests/test_packaged_mcp.py (wheel build, fresh install and the 0.6.0 upgrade fixture); they stop at assert uv because this worker container has no uv binary. Those tests pass in CI on this head: test (0.28.0) and test (0.45.1) both succeeded, as did CodeQL, Validate PR and Version policy.
• 127 relative links and anchors in the 9 changed Markdown files: 0 broken. CONTRIBUTING.md#working-in-this-repository exists.
• scripts/mw-version.py check --base origin/main passes with the component unchanged at 0.9.2rc1.

Publication is not part of this PR. No tag, release or package upload has been made, and PyPI still has no 0.9.x package. After this PR and the site PR merge, the existing Release workflow publishes the version carried by the merged main tip.

[timeleft--]

Reviewed the exact head against the accepted final canonical package and actual owning source. All nine changed files reviewed; full payload and reconstructed patches match, with the bounded Blueprint/FAQ continuity edits verified. Version policy remains 0.9.2rc1; 24 focused MCP context tests pass. All 12 hosted checks pass, including both required test runs and Validate PR from app 15368; no commit statuses or unresolved threads, current base verified. Source integration is clean. This approval does not establish package publication or final website acceptance.