Skip to content

Implement managed recovery and daily coding continuations - #123

Draft
vanedaltro wants to merge 88 commits into
mainfrom
feat/managed-recovery-owner
Draft

vanedaltro wants to merge 88 commits into
mainfrom
feat/managed-recovery-owner

Conversation

@vanedaltro

@vanedaltro vanedaltro commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Continues #93 with Location-bound managed snapshot recovery, reviewed keep/rollback operations and recovery clients, native worker receipts, durable settlement/reclamation work, and additional structured-output and JSONL ownership handling. It also adds trusted path-scoped rule delivery for successful reads, edits and completed patch effects, plus authenticated context inspection in the API and TUI.

This draft consolidates the remaining daily-coding work. The authoritative requirements and evidence are tracked in the OpenSpec tasks and the delivery audit. Remaining requirements include recovery construction/crash/reclamation and platform acceptance, exact rule configuration-generation and revocation handling, complete next-request context projection, and JSONL driver ownership, backpressure, hook events and restart/lost-acknowledgement acceptance. Managed Git admission remains gated. #92 retains its separate scope.

The latest context increment records estimates from the final assembled request, including turn instructions and callable schemas, and compares them with the request captured by a scripted provider. Inspection retains metadata across restart and omits source content by default.

For the context increment at 64052cb, selected local verification passed all 17 structured-output cases, 24 context/compaction cases, the authenticated HTTP inspection case, focused TUI rendering and stale-reply cases, OpenAPI/SDK consistency, SDK typecheck and 136 SDK tests with 10 configured skips. Server/TUI all-target Clippy passed with warnings denied. Strict OpenSpec passed 100 items and specification lint reported zero errors and 25 warnings. Native compiler/linker warnings were observed. Broader branch evidence and unperformed checks remain recorded in the delivery audit.

The first PR CI revision, 64052cb, failed Windows core lint because acknowledgement-retirement helpers compiled without their Linux/macOS native consumers. Revision 2a628f1 applies the matching platform condition to those helpers. Local core library/test Clippy and 17 acknowledgement/publication/retirement cases pass, with two configured subprocess fixture entries ignored by the ordinary harness. Windows binary-storage proof on 2a628f12 passed native core Clippy and all 25 selected binary tests with no skips. The remaining current-head PR checks, substantive review of the consolidated branch and the remaining acceptance work are required before readiness and delivery.

The broader Windows workspace lint on 2a628f1 subsequently reported unused Git-corruption fixture helpers whose callers are Unix-only. Revision 90234d3 applies the matching Unix condition to those helpers. Snapshot all-target Clippy and all 22 local Git snapshot integration cases pass; the single ignored harness entry is a subprocess fixture invoked by its parent test. Windows verification of this correction is pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant