[Kernel][G08] Serve authoritative state and reconnectable progress to CLI, Console and notifications #57
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#60 [Kernel][G01-G13] Accept the installed controlled-task path end to end
Creatidy/creatidy-kernel
#59 [Kernel][G11] Own concurrent tasks, workspaces and manual-edit reconciliation
Creatidy/creatidy-kernel
#106 Deliver ordinary Program execution with shared pull and managed push handoffs
Creatidy/creatidy-kernel
Reference
Creatidy/creatidy-kernel#57
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Priority: P1
Type: implementation/consumer integration.
This active scope supersedes conflicting historical descriptive scope, priorities and dependencies. The entire previous body is preserved unchanged under Historical Scope And Evidence; its evidence, unknowns, dispositions and review counters are not reset. PR #104 is integrated at
ace7175e087cd70e207594f5631c8f4f70fabfd4; historical pending wording is not current integration status. Prepared A/B are registered as #105/#106. Publication is not feature implementation or overall alignment acceptance.Goal
One authoritative command/status/event surface for work clients, push adapters, CLI/TUI, Console and optional IDE UI.
Why
Offline status opens exclusive SQLite and cannot be a concurrent active-controller API. Retain prior specification.
Scope
Shared application handlers, owner/worker/observer scopes, read projections, bounded progress and decision notifications; no frontend workflow engine, new scheduler or provider-wide schema.
Acceptance Criteria
Dependencies
Native predecessor plan: #59 and #106. #59 claim semantics and #106 for complete ordinary command composition. #59/#106 local work does not depend on this transport, eliminating the old #57/#59 cycle. Router #183/MI #16/Console availability are NOT Kernel producer prerequisites. Unselected remote security commitments are scoped decisions, not permission to invent auth or block the trusted local application core. Native edge publication is separate from this body amendment.
Constraints
ADR 0012 and ADR 0011 govern this work. Keep inward dependencies (
adapters -> ports -> core) and a self-contained public core. No new coding agent, tracker, catalogue, gateway or generic workflow DSL; no credential/runtime-state copying. Preserve old bytes, IDs and unknowns, all historical evidence and review counters, and #53 CLOSED/NOT IMPLEMENTED with PR #85 CLOSED/UNMERGED; its diagnostic is not accepted implementation. Require synthetic offline tests plus the installed path and fresh independent exact-subject review. Live inference/effects/releases require separate authority. Registration/publication grants no production credentials, paid/live execution, external mutation, release or deployment authority.The single active priority above follows the integrated Priority Contract: P1 is core authority/data-integrity foundation or complete everyday work capability on the critical path. Eligibility and evidence precede priority; P1 does not bypass prerequisites, owner decisions or STOP_REVISE. Historical descriptive priorities are superseded, not deleted. Excluded invalid/wontfix/duplicate dispositions and unchanged /loop ordering remain intact; this amendment selects no feature for execution.
Producer evidence correction supplied for this publication: SR develop
4a182affa4775a4a38b47860ad7622a099c56c4a, #222/PR #223, integrates default-off D-082 opt-in MI admission. It does not establish real-source positive adoption or expand this Kernel issue's external scope; Router/MI operation and policy remain their owners' responsibility.Links
ace7175e087cd70e207594f5631c8f4f70fabfd4).ace7175e08/docs/adr/0012-unified-work-coordination-and-drivers.mdace7175e08/docs/adr/0011-task-level-authority-and-trusted-development.mdace7175e08/docs/architecture/target.mdace7175e08/docs/architecture/migration.mdace7175e08/docs/architecture/backlog-alignment.mdace7175e08/docs/architecture/successor.md (g08-owner-served-state-boundary-planned); PR #95: #95 ; receipt: #57 (comment)Historical Scope And Evidence
Goal
Owner: Kernel state/command/event producer. Define and implement an owner-served view or controlled projection with coherent CLI/status/doctor and reconnectable progress semantics, plus authority-checked commands and meaningful decision notifications. Console/IDE are clients, not schedulers or SQLite peers. Source: shared architecture v1.0, sections 1-8, 9.2-9.4, 10-18 via #46 brief.
Why
Users should not monitor a dashboard continuously or open the live controller DB. UI/PWA/VS Code cannot themselves guarantee process/session/alert persistence; a stale view must not authorize commands.
Current Evidence
At
eb4f4a2956, sqlite_store.py holds a process/thread-owned EXCLUSIVE private connection for store lifetime. task_status/export_task open that store, so are not a concurrent served interface. CLI doctor/preflight have closed safe diagnostics; native Codex notifications are not public progress events. #5/#10/#44 are state/operator foundations, not a Console API. No current public snapshot/cursor/event transport exists.Scope
Specify then implement minimal owner-served snapshot/event/command boundary using existing durable facts; keep necessary state trace distinct from lossy progress and telemetry. Define read-from-position, deduplication, reconnect, bounded buffer, gap detection and snapshot resync; correlate task/Attempt/session/route/call/candidate. Explain current truth/freshness and concurrent tasks. Notification subscription/delivery has honest process/transport ownership and decisions/actions, not endless dashboard polling.
Acceptance Criteria
Reuse
Retain SQLite journal/projections, application semantics and doctor vocabulary. Evaluate existing native progress events, Rich for presentation and OpenTelemetry for diagnostics after exact revision/license/negative/security/dependency-maintenance checks; no broker or observability platform by default. Standard libraries and controlled projections preferred when sufficient.
Dependencies And Priority
Early state contract alongside #47 lifetime decision; consumers need #48/#54/#52 state/correlation semantics and actual #59 concurrent workspace ownership/#61 source-cache ownership. Each product serves its own state: Router #183 and MI #16 are analogous producer contracts, not permission to build Console here. Console counterpart not found at registration; authenticated consumer receipt remains expected and separate. No issue numbers are predicted.
Constraints And Permissions
No direct Console SQL, global ontology, shared DB, independent UI scheduler/ranking/auth store or weakened durability. Offline served-state tests need no inference; live notifications/service/network/external commands require separately scoped authority. Auth/retention/process-lifetime choices beyond accepted architecture require owner decision, not invented policy.
Links
Non-Goals
No Console implementation, new telemetry service/framework, dashboard-vigilance obligation or automatic effect authority.
Final Console Discovery
Canonical search at handoff found newly created public Creatidy/creatidy-console and actual issue Creatidy/creatidy-console#1, 'Bootstrap Creatidy Console: product architecture, repository foundation and integration backlog'. Its full body was read: AC map requirements to evidence/actual issues, establish make help/check+CI and independent bootstrap PR, and register producer dependencies without invented live views. This supersedes an absent-repository/counterpart inference, but is NOT a dedicated accepted snapshot/event/command consumer contract. No specific G08 conformance issue/receipt was found at this check. Console #1 owns registering that consumer slice; Kernel #57 still owns served state/current authority, and actual producer-consumer tests must precede reception. Console cannot read SQLite, schedule/rank or maintain permission truth. No Console file/issue/PR was modified by Kernel; no new cross-product API is approved.
Console counterparts are now registered under Creatidy/creatidy-console#1: #2 read/auth contract inventory, #3 resilient snapshots/progress/reconnect gaps, #4 task/overview evidence, #7 revision-bound owner responses, #9 attention, #12 conformance/live gates. These consumer tasks reuse this producer issue rather than duplicate it. Exact current-source constraints recorded: offline task_status/export opens exclusive SQLite; history/spec/aggregate revisions differ; identical command-key replay is historical receipt, not fresh current state. Console will not read active DB, infer timestamps/correlation, or prescribe an unreviewed endpoint. Registration changes no producer scope/implementation/authority.
The explicitly early, source-grounded G08 state-boundary specification is committed as
d1a061d4366cb6bfacfe492c3cf8acbca622d90aand submitted in PR #95: #95. It inventories the current exclusive SQLite/task status, provider pagination and transient Codex notification shapes, and marks owner-served snapshot/reconnect/command behavior as planned without choosing an API/auth/cursor/retention model.make checkandmake package-checkpassed. This is a partial preparation slice; issue #57 remains open pending producer correlation/concurrency and consumer-conformance gates.PR #95 is integrated in merge commit
f7db85188a0c20438f2b3e8ccbbeb28ada012425, with first parent base0c6f17e138111dd4ed78cdb817771eaee84d30a9and reviewed headd1a061d4366cb6bfacfe492c3cf8acbca622d90a; Git confirms the reviewed head is an ancestor of currentdevelop. Exact-head workflow #2917 succeeded; independent review ordinal 1/10 approved with empty findings;make checkandmake package-checkpassed on the approved tree. This integrates only the source-grounded planned boundary specification. The owner-served API/event/command implementation and full acceptance remain gated, so issue #57 stays open.kilo referenced this issue2026-10-28 00:58:52 +00:00
Owner Forgejo-First Acceptance Interpretation, 2026-10-29
Owner explicitly sequences complete ordinary Forgejo pull/push work in #106 before heterogeneous #105. For #57, its native prerequisites remain #59 and #106, and installed/local producer/consumer conformance must receive the actual Forgejo-first #106 path; do not infer that deferred #105, Console, Router or MI is required to implement trusted local state/commands. Remote authentication/exposure remains required before enabling remote transport. Preserve the full existing six acceptance criteria, historical body/evidence and later replaceable-provider capability; this interpretation does not claim #57 implemented or waive future heterogeneous reception. It is the owner's later explicit decision, not a change to ADR 0012.
kilo referenced this issue2026-10-30 17:51:49 +00:00
Fresh /loop Selection After #106 Acceptance
Owner-authorized final #106 recovery integrated via PR113 merge
fce1c0d4d63fdf4ca0673512c9b9d2512f0ac023; active AC1–6 and exact reviewed/tested tree are received in #106comment20200. Original PR112 remains closed/unmerged with permanent10/10 STOP_REVISE; distinct recovery used2/4 (REQUEST_CHANGES, APPROVE). No live product GO is inferred.Fresh canonical /loop SELECT exhausted open issues, applied exact invalid/wontfix/duplicate exclusions before history, refreshed actual bodies/comments/native edges and verified producer receipts. #57 is selected as the highest-priority eligible P1: native predecessors #59 and #106 are accepted/integrated through PR110/issue59comment19620 and PR113/issue106comment20200, respectively. #58 and #62 are independent eligible P2 candidates; #105 remains P3 explicitly owner-deferred, PR111 unmerged7/10, and #60's full heterogeneous/strict acceptance remains unreceived. Console, Router/MI producer availability and deferred #105 are not whole-issue prerequisites for #57's trusted local core; remote authentication/exposure must be received before enabling remote transport.
Post-selection actual #57 OPEN/P1/body/deps unchanged. Normal branch
issue-57-owner-served-statestarts at freshly fetched exactdevelopfce1c0d4d63fdf4ca0673512c9b9d2512f0ac023in the same clean checkout. The previously integrated PR95 was specification only; its independent review ordinal 1/10 remains consumed and is not reset. The next whole-PR review, when warranted after implementation/gates, will be ordinal2/10.Implement actual active AC1–6 owner-held state/projection, scoped commands and bounded reconnect/replay/gap semantics with installed client conformance; no second SQL reader, frontend scheduler, speculative remote security or new orchestration framework. Do not infer that this selection accepts any implementation. Issue remains OPEN until fresh independent review, exact CI/currentness and integrated acceptance gates.
Implementation PR #114 is open against
developatbf812cbbcad93280ca39a52f65a50baeedc14000(basefce1c0d4d63fdf4ca0673512c9b9d2512f0ac023). Sanitizedmake checkpassed (2420 tests, 89 optional skips, 106 subtests);make package-checkandmake auditpassed. The local descriptor capability does not enable remote exposure and does not equate disconnect or cooperative quiescence with physical settlement. Independent whole-PR review and exact-head CI remain pending; issue remains open.Delivery of PR #114 stopped at STOP_REVISE 10/10. The final independent whole-PR review of
9e4c12d5d830525b2e0c0b598b325fb277b19fb1againstfce1c0d4d63fdf4ca0673512c9b9d2512f0ac023identified two unresolved P2 issues: (1) a reentrant Program revision change during final workspace observation can be missed by preparation admission; (2) per-Attempt notification deduplication can suppress the later actionable decision after areview_unknownalert. The reviewer independently passedmake check(2444 tests, 89 optional skips, 106 subtests) andmake package-check; these passing checks do not resolve the findings. The PR remains open and unmerged and the issue remains open. No further review or remediation is authorized by the exhausted delivery budget.Owner-authorized distinct recovery is open as #115, superseding closed unmerged #114 without resetting its 10/10 STOP_REVISE history. Both reported counterexamples were reproduced before correction; full sanitized
make check,make package-check, andmake auditpassed on recovery HEADa6b6f614e85e797707bf96caa9ddc25481395651. The separate recovery review budget is 0/4 and independent whole-PR review remains pending.Integrated acceptance: PR #115 merged to
developasda9c736fe61ba33c3d1889f15949948928eb4dea. Its parents are approved basefce1c0d4d63fdf4ca0673512c9b9d2512f0ac023and approved HEAD96af53b843722d6db0749d10d448ced2c23684a4; the merge tree exactly matches the approved HEAD tree. Fresh independent GPT-6.1 Sol High whole-PR review 4/4 returned APPROVE with no findings for those exact refs. Exact-head CI run 281 succeeded; sanitizedmake checkpassed 2453 tests, 89 optional skips, 106 subtests,make package-checkpassed, andmake auditfound no known vulnerabilities.The delivered owner-thread local capability, bounded state/reconnect semantics, shared-handler scoped commands, versioned contract and installed client satisfy the active local acceptance criteria. The two explicitly authorized recovery regressions were reproduced before correction and pass after it. This is not remote exposure, live inference, hostile same-UID isolation, downstream Console/IDE implementation, or production GO. Original PR #114 remains closed unmerged with its independent STOP_REVISE 10/10 history unchanged; recovery used 4/4 reviews.