feat(go): expose retained incident views

This commit is contained in:
Luna 2026-07-22 03:12:34 -07:00
parent eff31b3a82
commit 6355fb403d
No known key found for this signature in database
6 changed files with 166 additions and 7 deletions

View file

@ -1,8 +1,8 @@
# Go Port Handoff
Saved: 2026-07-22T02:22:00-07:00
Saved: 2026-07-22T02:34:00-07:00
Branch: `main`
Base commit: `1ab4add` (`feat(go): chain retained snapshot artifacts`)
Base commit: `eff31b3` (`feat(go): enrich snapshots asynchronously`)
Status: implemented and green, but uncommitted
## Worktree warning
@ -10,9 +10,10 @@ Status: implemented and green, but uncommitted
The checkout is intentionally dirty and contains work from multiple related
continuations. Do not reset, clean, or broadly restage it.
- The validation-sidecar, incident-persistence, bounded-enrichment, and local-
assurance tranches are signed commits `f85c2e8`, `538d1d9`, `fd2bbba`, and
`1ab4add`. The asynchronous-enrichment slice is uncommitted.
- The validation-sidecar, incident-persistence, bounded-enrichment, local-
assurance, and asynchronous-enrichment tranches are signed commits
`f85c2e8`, `538d1d9`, `fd2bbba`, `1ab4add`, and `eff31b3`. The native
incident-reader slice is uncommitted.
- At this checkpoint, `git status --short` has 20 entries with untracked
directories collapsed.
- The Python GUI files and tests are separate pre-existing work. Preserve them
@ -104,6 +105,9 @@ static binary.
outside the snapshot lock; a full queue simply leaves optional fields unknown.
- Package ownership, richer integrity anchors, and notification fan-out are not
yet ported.
- `--incidents-list` and `--incident-show <id>` now read the sidecar's isolated
state without starting the agent. The latter returns `enodia.incident.view.v1`
with the incident, available snapshots, and time-ordered timeline.
- No live system service was installed or enabled during development.
## Last green verification
@ -150,8 +154,8 @@ the suite still exits successfully.
1. Add bounded package-ownership and integrity-anchor collectors to the existing
asynchronous worker without destructive response behavior.
2. Connect the isolated Go snapshot/event state to explicit read-only
management consumers while keeping Python authoritative.
2. Add a read-only management API consumer for isolated Go snapshot/event state
while keeping Python authoritative.
3. Continue broader Phase 3 rule metadata/state parity before considering any
default-service or package cutover.