[yia-mw-agent]

Promotes the current main candidate to stable (refs #147). Merge when clean: no (First Officer owns Wednesday 16:00 promotion pass).

Refresh after review (changes requested on 12e001a): main advanced b2e7f0b -> f1c89ae (#148, which also bumped the candidate 0.8.4rc1 -> 0.8.5rc1), so the original 0.8.4 promotion conflicted. This branch now has a normal merge of origin/main (66cc946, no force-push/rebase) and a recalculated suffix-only promotion (d5ed119).

Change: python3 scripts/mw-version.py update --base origin/main --title "chore(release): promote version" -> repo: 0.8.5-rc.1 -> 0.8.5. Only the 3 configured mirrors differ from main f1c89ae (pyproject.toml, src/fava_trails/init.py, uv.lock), 1 line each: 0.8.5rc1 -> 0.8.5. No semantic base increment in this PR; no workflow/dependency/pin changes.

Exact non-version delta from Monday candidate b2e7f0b (v0.8.4rc1) to this head: all from merged #148 (startup-instruction trim, resolves #146), nothing else:

• AGENTS.md (2/2), AGENTS_USAGE_INSTRUCTIONS.md (5/3), CHANGELOG.md (3/0), docs/mcp-context-overhead.md (11/12)
• src/fava_trails/mcp_context.py (25/63), src/fava_trails/server.py (2/2)
• tests/test_mcp_context.py (27/18), tests/test_server_instructions.py (50/9)
  git diff --numstat origin/main HEAD shows exactly the 3 version files; git diff --numstat b2e7f0b HEAD shows those 3 plus the 8 files above.

Evidence gap to review: this promotes #148 product bytes to stable. 0.8.5rc1 has not been tagged, published, or installed (only v0.8.4rc1 exists), so those bytes have only CI/test evidence, not multi-day installed MCP evidence like the Monday candidate.

Verification on head d5ed119 (jj 0.45.1, uv 0.12.3, JJ_CONFIG=/dev/null):

• mw-version.py check (title above, base origin/main): Version policy passed
• ruff check src/ tests/: passed
• tests/test_packaged_mcp.py + test_release_channels.py + test_mcp_context.py + test_server_instructions.py: 100 passed (wheel-from-sdist, installed CLI/MCP identity)
• full suite excluding packaged_mcp: 1155 passed

Worker does not merge, tag, publish, install or restart.

[timeleft--]

Current head 12e001a is now conflicting with main after separately merged #148. Please refresh this SAME PR through a normal integration, recalculate the suffix-only promotion against actual main with the repository updater, and report the exact non-version delta from Monday candidate b2e7f0b. Retain the existing administrative merge restriction; this is source repair only, no merge/tag/publication/install. Reuse valid packaging evidence and rerun affected current-source checks; do not silently promote untested newer product or repeat a semantic base increment.

[yia-mw-agent]

Addressed review 5533620027 on the same PR and branch (fast-forward push 12e001a..d5ed119; no rebase or force-push).

• Integration: normal merge of origin/main f1c89ae (66cc946); conflicts were version-only, resolved to main's side so the merge tree equals main.
• Promotion recalculated with scripts/mw-version.py on actual main: 0.8.5-rc.1 -> 0.8.5 (docs: slim FAVA startup guidance, keep detail in usage guide #148 had already bumped the candidate to 0.8.5rc1, so the old 0.8.4 target no longer applied). Head d5ed119 differs from main only in the 3 version mirrors, 1 line each.
• Non-version delta from Monday candidate b2e7f0b: only merged docs: slim FAVA startup guidance, keep detail in usage guide #148 (AGENTS.md, AGENTS_USAGE_INSTRUCTIONS.md, CHANGELOG.md, docs/mcp-context-overhead.md, src/fava_trails/mcp_context.py, src/fava_trails/server.py, tests/test_mcp_context.py, tests/test_server_instructions.py). PR body lists line counts.
• Evidence gap: 0.8.5rc1 was never tagged/published/installed, so docs: slim FAVA startup guidance, keep detail in usage guide #148 bytes have CI and local test evidence but no installed-MCP soak like v0.8.4rc1. Whether to promote them as-is is the First Officer's call.
• Re-run on d5ed119: Version policy passed, ruff clean, packaged_mcp/release_channels/mcp_context/server_instructions 100 passed, full suite excluding packaged_mcp 1155 passed. GitHub checks all pass; PR is MERGEABLE.
• Administrative merge restriction unchanged. No merge/tag/publish/install/restart.

[timeleft--]

Oct16 exact-head re-review at d5ed119: the requested source refresh and explicit delta accounting are addressed. Independent current-main version-policy check passes; diff from main is only the three configured suffix-removal mirrors. Independent Python3.13 frozen-environment tests for release channels, affected MCP context/server instructions and packaged MCP pass: 100 tests. Hosted current-head checks also pass. This does not establish installed actual-use evidence for the newer 0.8.5rc1 product bytes; the installed weekly candidate remains 0.8.4rc1. Existing administrative merge restriction is unchanged. No merge, publication or installation performed.

[timeleft--]

Independent exact-head approval d5ed119 against f1c89ae. Three configured version mirrors only remove the0.8.5rc1 suffix; no semantic base increment or product delta versus currentmain. Reuse still-valid independent current-baseVersionpolicy and100 packaged/release-channel/MCP instruction tests from Oct16, unchanged head. Oct19 exact f1c89ae postmerge Tests38627364952 now SUCCESS bothJJmatrices after failed-jobs-only recovery of pre-test API403. Immutable v0.8.5rc1 workflow39257461467 SUCCESS; public GitHub/PyPI wheel+sdist bytes match; actual installed candidate all66payloadfiles match and MCPinitialize/17tools/guide/isolatedsave-recall/governed-isolation pass. Existing current candidate rollback0.8.4rc1 wheel/dependency/runtime proof retained. This is source approval only; existing147 administrative merge restriction and Wednesday promotion timing remain unchanged. No stable merge/publication/deployment authorized by this review alone.