pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream)

Gap

The PM stack has no first-class event log. The audit/activity pieces exist but are scattered across separate stores in the aggregator state dir (~/.local/state/pm-aggregator/):

the actions store (dashboard triage actions + their applied outcomes)
the orchestrator's published actions[] in orchestration.json
the session registry (agent/session identity + outcomes)
the dashboard comments store (note / message / github kinds)
per-item derived activity (derive.ts merges linked refs' comments — but comment resolution depends on the projector, which is not deployed; see code#1199)

There is no single chronological "what happened across the stack" stream a human (or the /today page) can read.

What to build

An append-only event record in the aggregator: {at, actor (drew / orchestrator / keeper / job id / session), kind (action-applied, tier-change, comment, session-outcome, status-write, wall, ...), ref (item/session/goal), summary}.
Writers: the aggregator's own action-result route, the orchestration publish step, and the session registry merge — events are emitted where the facts already occur, not scraped afterward.
A page + machine-first /api twin (e.g. /events and /api/events.json) with filters by kind/ref/actor, newest first, bounded retention (e.g. 30 days or N=5000, whichever first).
/today links its "progressed since last run" entries to the underlying events.

Acceptance

Dashboard actions, orchestration tier changes, and session outcomes all appear in one stream with timestamps and refs.
The /api twin carries the same records; filters work.
Writing an event never blocks the underlying action (fire-and-forget append with the same durability as the existing stores).

Raised by Drew 2026-10-28 in the PM-stack non-Git data review; companion to the roadmap-files integration issue filed the same day.

Acceptance criteria

Dashboard actions, orchestration tier changes, and session outcomes all appear in one chronological stream with timestamps and refs.
The /events page and its /api/events.json twin carry the same records; filters by kind/ref/actor work.
Writing an event never blocks the underlying action (fire-and-forget append with the same durability as the existing stores); retention is bounded (e.g. 30 days or N=5000, whichever first).

CODE-702

Acceptance clarification (Drew, 2026-10-28): the event stream needs a front-end endpoint too, not only the API — a user-facing /events page in the dashboard (chronological stream, filterable by kind/ref/actor in the UI, linked from /today's progress entries) in addition to the machine-first /api/events.json twin. Both are required; an API-only delivery does not close this issue.

Intake review

Related: #1744 (shared PM-stack schema — this log should be designed against it), #1738 (roadmap files, companion filed the same day), #1199 (projector not deployed; per-item derived activity depends on it).

Notes: Verified still live at intake (2026-10-28T17:45Z): no cross-stack event log exists; the scattered stores named in the body (actions store, orchestration.json actions[], session registry, comments store) are the current state. Acceptance criteria section appended formalizing the body's ## Acceptance list; original body preserved above it.

Risks: Writing events at three separate emission points can double-count if the orchestration publish and the session-registry merge both fire for one fact — pick a single emitter per fact. Retention bound must be enforced from day one or the append-only file becomes the next unbounded store.

Suggested approach: Define the event record + append helper in the aggregator first, wire the action-result route as the first writer, ship /api/events.json with the page, then add orchestration and registry writers.

🤖 Fleet monitor intake enrichment · 2026-10-28

🤖 Agent note · picked up

Agent: repo-worker-code, OpenChamber scheduled lane
Session / ID: queue task 2631 (triage)
Found via: atomic queue claim (repo-health-code-pilot)
Task: Revalidate pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739 against current main and route only if no active owner or duplicate work exists.
Expectation: triage verdict and any follow-up recorded; no competing PR if related work is already owned.
Links: pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739

🤖 Agent note · parked

Agent: queue worker (repo-worker-code), lane K
Session / ID: task 6400
Found via: queue claim (resume from park)
Task: all 3 Codex re-review P2 findings on PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 are fixed in commit 49900bf and dispositioned with replies on each finding thread (parsed-time sort in filterEvents; actor/ref identity constraints aligned with the action-result and isObjectRef contracts; retention tests now use relative timestamps, with regression tests for all three). Aggregator suite: 1221 pass, 2 pre-existing failures verified identical on the clean PR head. Task 6400 parked 20m because the basic guard check (run 41560051930) is still queued with no runner after the 5-minute poll window.
Expectation: resume when the guard is green on head 49900bf and Codex is clean on that head — then merge PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 and complete task 6400 as fixed_merged
Links: PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489, issue pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739, task 6400

🤖 Agent note · parked

Agent: queue worker (repo-worker-code), lane code-i
Session / ID: task 6400
Found via: queue claim (resume of parked task)
Task: task 6400 / issue pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739 — merge PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 (aggregator cross-stack event log) once its gates clear
Revalidation (fresh, 2026-11-03T02:44–02:50Z): PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 OPEN, MERGEABLE, head 49900bf unchanged. Guard check (run 41560051930) still pending in the repo-wide CI runner jam — not a failure of this change. BUT the Codex re-review round at 01:34Z left two undispositioned findings on the current head: a P1 (deployed event store defaults inside the checkout; PM_AGG_EVENTS_FILE not wired in install.sh) and a P2 (orchestration actions with free-text targets are dropped by event validation). Both are accepted as real, in-scope bugs; replies are posted on both threads. Per the Codex findings gate, PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 must not merge past them.
Expectation: parked — resume by fixing both findings on branch queue/6400-1739-event-log (laptop worktree /home/user/git/fleet/6400), re-push, confirm Codex clean + guard check, then merge and complete task 6400 as fixed_merged.
Links: PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 · issue pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), lane code-k
Session / ID: task 6400
Found via: queue claim (resume from codex_findings_open checkpoint)
Task: Fix the two accepted Codex findings on PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 — P1: wire PM_AGG_EVENTS_FILE into aggregator/install.sh state-directory config so the deployed event store lives outside the checkout; P2: preserve orchestration actions whose free-text targets contain spaces (normalize into valid event refs instead of dropping the event). Then re-push, confirm Codex clean, and merge.
Expectation: effort/m; done = PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 merged, issue pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739 closed.
Links: PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 · issue pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739

fix(pm-agg): wire PM_AGG_EVENTS_FILE in install.sh; preserve free-tex…

Merge pull request #4489 from developing-today/queue/6400-1739-event-log

🤖 Agent note · done

Agent: queue worker (repo-worker-code), lane code-k
Session / ID: task 6400
Found via: queue claim (resume from codex_findings_open checkpoint)
Task: Done — PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 merged (merge commit 4ab8889). This shift fixed the final two Codex findings in 9b6ce98: P1 — install.sh now writes PM_AGG_EVENTS_FILE=${STATE_DIR}/events.json so the deployed event store lives outside the checkout; P2 — orchestration action targets pass through orchestrationActionRef (free text slugified, e.g. "fleet queues" → "fleet-queues") so their events are preserved instead of dropped by validation. Both Codex threads replied with the fix dispositions; Codex re-review on 9b6ce98 completed with no findings.
Expectation: met — laptop bun tests: orchestration + events 49 pass; full aggregator suite 1222 pass / 2 pre-existing fails (manifest tier table, derived briefs — disjoint from this diff, previously verified on clean head). The metered-provider guard run was cancelled in the Actions runner jam (no adverse verdict); merge proceeded under the standing authority on verified tests + clean Codex.
Links: PR feat(pm-stack): cross-stack event log — EventsStore, writers, /events + /api/events.json (#1739) #4489 · issue pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739

Navigation Menu

Repository navigation

pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739

Gap

What to build

Acceptance

Acceptance criteria

Intake review

247 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

pm stack: one cross-stack event log (actions, orchestration, sessions, comments in a single chronological stream) #1739

Description

Gap

What to build

Acceptance

Acceptance criteria

Activity

developing-today commented on Oct 28, 2026

dezren39 commented on Oct 28, 2026

dezren39 commented on Oct 28, 2026

Intake review

dezren39 commented on Nov 1, 2026

247 remaining items

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions