docs: specify owner-served state boundaries (#57) #95
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-57-owner-state-spec"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
This is the explicitly early, source-grounded specification slice for #57. It records the current authoritative Kernel state and progress surfaces (
SQLiteProgramStore,AttemptSpec/operations/artifacts, one-shottask_status/export_task, providerPage.next_cursor, and transport-scoped Codex notifications), and separates those facts from the planned owner-served state/reconnect semantics.No API, endpoint, transport, event schema/cursor representation, authentication/grant, retention or process-lifetime choice is made. No service, event store, consumer database access, command path, or live behavior is added. Full owner-served implementation, route/call correlation, concurrency, Console conformance and owner-controlled decisions remain outstanding; issue #57 stays open and this PR does not claim full acceptance.
Validation
make check: 1457 passed, 85 skipped, 106 subtests; Ruff, basedpyright, import boundaries, secret scan and diff checks passed.make package-check: reproducible wheel/sdist, isolated install, and CLI/intake/source smoke checks passed.Refs
Refs #57
Base:
0c6f17e138111dd4ed78cdb817771eaee84d30a9Head:
d1a061d4366cb6bfacfe492c3cf8acbca622d90aNo live Console access, inference, telemetry or external effect was used.