docs(state): rewrite STATUS_NOW.md as live dashboard for next-claude wake-up #106

Merged

pdurlej merged 1 commit from claude/orders/status-now-dashboard into main

2026-05-08 23:25:12 +02:00

claude commented

2026-05-06 00:30:50 +02:00

Collaborator

Canary status: missing — Small PR class (state/ markdown only, no governance/module/control-plane changes); operator may operator_override given context

Purpose

Persistent dashboard for orchestrator state. Operator-requested 2026-05-05 ("dashboardlight") and operationally needed 2026-05-06 ("force push platformy dzisiejszej nocy"). Previous content was from 2026-05-02 glm-strive session — fully stale, referencing PRs that since either merged or were superseded multiple times over.

What changed

Rewrote state/STATUS_NOW.md from 201 lines (stale) to 80 lines (current).
Mobile-scannable: 30-second readback for operator + orchestrator wake-up
Captures: operator intent (with quote), Decision Queue, Open PRs/Issues by lifecycle label, Active Codex tracks, Recently merged, Standing context for next claude session
Replaces multi-section sprawl with single-thread narrative

Why

Recovers from post-context-compaction failure mode: future-claude waking up to fresh session must currently reconstruct state by scanning all open PRs + issues + recent commits, burning tokens on something that should be a 1-file read.

With STATUS_NOW.md current, wake-up cookbook becomes:

Read state/STATUS_NOW.md (30 sec)
Optionally git log origin/main..HEAD for delta since Updated: timestamp
Resume work

Vs current cost: ~10-15 API calls + ~5min reconstruction. The savings compound across sessions.

Plus operator's chat 2026-05-06: "jak coś budzisz się po długiej przerwie, więc zaktualizuj najpierw, zobacz jak wygląda status platformy" — this file is the answer to that prompt.

Files touched

state/STATUS_NOW.md (rewrite, +80 / -201)

Relevant context

AGENTS.md (canonical agent cookbook — STATUS_NOW.md is its operator/orchestrator-side counterpart)
state/agent-execution-template.md (PR #69, referenced by lifecycle-label entries in this file)
state/glm-sunset-watch.md (PR #69, lessons-learned referenced in standing-context wake-up checklist)

Runtime evidence

N/A — pure docs change. No runtime impact.

Known constraints

File is currently maintained manually. Operator's chat noted future automation: state/refresh-status-now.sh would query Forgejo API + rebuild from PR/issue data. Out of scope for this PR.
Snapshot is point-in-time (Updated: 2026-05-06). Drifts as PRs merge / issues open. Mitigation: end-of-session regeneration; live Forgejo always wins on contradiction (noted in file footer).

Explicit out-of-scope

state/refresh-status-now.sh automation script
OPERATOR.md (counterpart-for-piotr; suggested in chat, deferred to follow-up)
Any AGENTS.md or PLATFORM_CHARTER.md amendments referencing STATUS_NOW.md (follow-up if pattern proves valuable)
Any module manifest / control-plane / decisions/ changes

Requested decision

approve_merge — Small PR class, doc-only, no canary required by ADR 0001 paths definition. Operator may operator_override per Rule 2 if needed for force-push-tonight cadence.

Spec sources read

state/STATUS_NOW.md (pre-rewrite, full file) — to know what was there + decide rewrite vs amend
AGENTS.md (skim, §Joining as a new agent + §Anti-patterns) — to confirm STATUS_NOW positioning as operator/orchestrator-side counterpart
state/agent-execution-template.md — referenced in standing-context section
state/glm-sunset-watch.md — referenced for modelizm anti-pattern reminder
Forgejo open PRs + issues (live API query) — to populate snapshot tables accurately
Recent main commits (git log origin/main --oneline -15) — to populate "Recently merged" section
Operator chat 2026-05-06 — for intent quote and Decision Queue execution status

Test plan

Operator readback: STATUS_NOW reads as 30-second wake-up doc (not 5-minute report)
Operator readback: Decision Queue + Active Codex tracks sections feel correct
After merge: next claude session opens with Read state/STATUS_NOW.md as first move (verify cookbook works)

Canary status: missing — Small PR class (state/ markdown only, no governance/module/control-plane changes); operator may operator_override given context ## Purpose Persistent dashboard for orchestrator state. Operator-requested 2026-05-05 ("dashboardlight") and operationally needed 2026-05-06 ("force push platformy dzisiejszej nocy"). Previous content was from 2026-05-02 glm-strive session — fully stale, referencing PRs that since either merged or were superseded multiple times over. ## What changed - Rewrote `state/STATUS_NOW.md` from 201 lines (stale) to 80 lines (current). - Mobile-scannable: 30-second readback for operator + orchestrator wake-up - Captures: operator intent (with quote), Decision Queue, Open PRs/Issues by lifecycle label, Active Codex tracks, Recently merged, Standing context for next claude session - Replaces multi-section sprawl with single-thread narrative ## Why Recovers from post-context-compaction failure mode: future-claude waking up to fresh session must currently reconstruct state by scanning all open PRs + issues + recent commits, burning tokens on something that should be a 1-file read. With STATUS_NOW.md current, wake-up cookbook becomes: 1. Read `state/STATUS_NOW.md` (30 sec) 2. Optionally `git log origin/main..HEAD` for delta since `Updated:` timestamp 3. Resume work Vs current cost: ~10-15 API calls + ~5min reconstruction. The savings compound across sessions. Plus operator's chat 2026-05-06: "jak coś budzisz się po długiej przerwie, więc zaktualizuj najpierw, zobacz jak wygląda status platformy" — this file is the answer to that prompt. ## Files touched - `state/STATUS_NOW.md` (rewrite, +80 / -201) ## Relevant context - AGENTS.md (canonical agent cookbook — STATUS_NOW.md is its operator/orchestrator-side counterpart) - state/agent-execution-template.md (PR #69, referenced by lifecycle-label entries in this file) - state/glm-sunset-watch.md (PR #69, lessons-learned referenced in standing-context wake-up checklist) ## Runtime evidence N/A — pure docs change. No runtime impact. ## Known constraints - File is currently maintained manually. Operator's chat noted future automation: `state/refresh-status-now.sh` would query Forgejo API + rebuild from PR/issue data. Out of scope for this PR. - Snapshot is point-in-time (Updated: 2026-05-06). Drifts as PRs merge / issues open. Mitigation: end-of-session regeneration; live Forgejo always wins on contradiction (noted in file footer). ## Explicit out-of-scope - `state/refresh-status-now.sh` automation script - OPERATOR.md (counterpart-for-piotr; suggested in chat, deferred to follow-up) - Any AGENTS.md or PLATFORM_CHARTER.md amendments referencing STATUS_NOW.md (follow-up if pattern proves valuable) - Any module manifest / control-plane / decisions/ changes ## Requested decision `approve_merge` — Small PR class, doc-only, no canary required by ADR 0001 paths definition. Operator may operator_override per Rule 2 if needed for force-push-tonight cadence. ## Spec sources read - `state/STATUS_NOW.md` (pre-rewrite, full file) — to know what was there + decide rewrite vs amend - `AGENTS.md` (skim, §Joining as a new agent + §Anti-patterns) — to confirm STATUS_NOW positioning as operator/orchestrator-side counterpart - `state/agent-execution-template.md` — referenced in standing-context section - `state/glm-sunset-watch.md` — referenced for modelizm anti-pattern reminder - Forgejo open PRs + issues (live API query) — to populate snapshot tables accurately - Recent main commits (`git log origin/main --oneline -15`) — to populate "Recently merged" section - Operator chat 2026-05-06 — for intent quote and Decision Queue execution status ## Test plan - [ ] Operator readback: STATUS_NOW reads as 30-second wake-up doc (not 5-minute report) - [ ] Operator readback: Decision Queue + Active Codex tracks sections feel correct - [ ] After merge: next claude session opens with `Read state/STATUS_NOW.md` as first move (verify cookbook works)

claude added 1 commit

2026-05-06 00:30:50 +02:00

docs(state): rewrite STATUS_NOW.md as live dashboard for next-claude

canary-required / collect-diff (pull_request) Failing after 3s

Details

canary-required / canary (pull_request) Has been skipped

Details

274b231486

Operator-requested 2026-05-05 ("dashboardlight") and operationally needed
2026-05-06 ("force push platformy dzisiejszej nocy"). Previous content
was from 2026-05-02 glm-strive session, fully stale.

New content (~150 lines, mobile-scannable):
- Operator intent in one sentence (with quote)
- Decision Queue items pending operator UI work
- Open PRs + Issues snapshot by lifecycle label
- Active Codex tracks (self-decomposing subsystems)
- Recently merged (last 24h)
- Standing context for next claude session (wake-up checklist)
- Files-to-maintain pointer + regeneration note

Counterpart to AGENTS.md (cookbook for agents) — STATUS_NOW.md is the
30-second state readback for orchestrator + operator. Living doc;
regenerate at end of each meaningful session.

Recovers from post-context-compaction problem: future-claude reads this
file first, has full context, doesn't waste tokens reconstructing state
from PR/issue scans.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>