feat: consolidate TraceDecay V2 PR8-PR13 delivery - #421
feat: consolidate TraceDecay V2 PR8-PR13 delivery#421ScriptedAlchemy wants to merge 6961 commits into
Conversation
|
e50f8f5 to
4f5ab66
Compare
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 986f25cca6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
5862bd6 to
53502de
Compare
642a33a to
5f2f610
Compare
76dee0f to
0258866
Compare
062285a to
b73f8bf
Compare
1486ceb to
f44f5c5
Compare
The journey recorded the daemon-hosted dashboard as ungradeable after a physical restart: relaunching reported a fresh bound URL that never accepted a connection. 58d62d9 removed that cause -- McpServer shutdown was tearing down the process-global DASHBOARD_MANAGER whenever the Core->Full remount retired the warming server, which is exactly the window a post-restart launch binds in. The limitation note outlived the defect, so the durability pass still graded the daemon mount alone. It now relaunches the launcher against the restarted daemon, polls the fresh URL to serving, and grades every temporal mode on both mounts again, so a dashboard that stops resuming fails here instead of going unnoticed.
Regenerated the contracts from the Rust schemas and updated the graph fixtures so the covered-slice disclosure reaches the rendered surface rather than being dropped at the wire boundary. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A markdown heading is one graph symbol, but a heading alone answers nothing: a plan document is a work ledger. Sections now publish a truncated body preview, their 1-based line span, the parsed section structure (checklists with checked state, nested bullets, ordered steps, tables, block quotes, fenced code), and a retrieval id for the full body minted through the existing response-handle cache that reversible MCP truncation already uses. A handle is minted only when the preview truncates, and a per-response budget bounds the durable writes, so an outline never becomes a burst of fsyncs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Replaces the assertion that a narrower selection refuses the whole read. The covered prefix now reads with a Partial disclosure naming the scoped event beside it, a widened selection reads the same journal whole, and a mutation over the slice is refused as SelectionCoverageIncomplete. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The journey created its task under the repository selection because the no-Git selection refused every read once a settled attempt published repository-scoped events. It now creates under the no-Git selection, as a profile owner's work really begins, and grades the ruled behaviour on the live mount: the read answers its covered slice with a partial disclosure naming the boundary, the scoped relation is not folded into it, the mutation is refused by a problem that states the cause and the remedy, and the widened selection reads the same journal whole. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
retained_store_runtime_registry is platform-neutral and its caller is ungated; the global-db test harness now creates graph runtimes through the owner-attachment authority like production, clearing the ~154-test mount cascade. Also repair two dashboard-api test expectations: explorer knowledge-source coverage now asserts complete with exact totals, and the curation receipt assertion reads the typed detail field.
Host hook tests now assert initialization leaves no .tracedecay working-tree state, treat the .git/ repository identity marker plus the registry row as the project's durable anchors, and expect the cursor synchronous walk to resolve through the marker; losing both anchors still stops resolution entirely.
Existing-store attach re-runs the shared admission classification and idempotent install, restoring each authority's exact typed ResetRequired identity (ProfileResetRequired component "LCM" among them) that the owner-lifetimes refactor dropped; updates a test that encoded the deleted bare-installer authority expectation.
The truncated-envelope failure test wrote .tracedecay/enrollment.json into a temp working tree, which the git-marker identity cutover no longer reads; it now pins the profile root beneath a regular file so every durable handle-store write honestly fails, restoring the original env var on drop.
drop needless returns in renameat2 tails; raise Windows build and MCP smoke budgets that were killing healthy runs; pin the delivery fixture default branch; mount configuration and retained runtimes in the dashboard automation test authority so retained settlement is reachable.
PRAGMA shrink_memory now dispatches to the owning reader pool instead of the writer actor; handles that cannot release report a typed no-op instead of writer-unavailable, clearing the boot-time degraded event.
The dashboard-api test-transport gate hid DashboardHostAdmissionTestAuthorityV1 from production, but accounting_test_support still referenced it.
0349d3a to
c154597
Compare
Summary
This draft PR is the consolidated delivery branch for TraceDecay V2 PR8 through PR13.
The branch also contains the supporting rusqlite runtime cutover, worktree-aware incremental indexing, storage retention/Doctor integration, and direct product tests required by the canonical V2 plans.
Verification
cargo check --all-featurescargo test --all-featurescargo clippy --workspace --all-targets --all-features -- -D warningscargo fmt --all -- --checkCurrent status: implementation is still being consolidated from the shared checkout and CI is red. This PR remains draft until the working tree is committed, broad verification is stable, and the historical conventional-commit blocker is resolved. It must not be merged in its current state.
Safety boundaries
GitHub review ingestion is read-only. Semantic indexing never blocks exact/lexical/graph retrieval and publishes only complete compatible generations. Local coordination logs, private transcript evidence, secrets, and ad hoc artifacts are excluded from commits.