Make /roundup's tracked STATUS.md snapshot its default, committed output

Promote STATUS.md from an opt-in offer to standard behavior: every /roundup run now writes the report to ~/Projects/standards/STATUS.md (overwritten), shows it inline, and commits + pushes only that file so the portfolio state is diffable over time — the same durability reflex as /capture. STATUS.md remains the only file roundup writes; all project repos stay read-only. Updates guide (new Phase 4), wrapper, ROADMAP item 2, README, and Current state.
This commit is contained in:
Keysat
2026-06-14 14:14:07 -05:00
parent 8548afd9fd
commit b7625c4e83
5 changed files with 39 additions and 17 deletions
+24 -6
View File
@@ -42,13 +42,14 @@ existing one.
Wait for all readers before synthesizing. If a reader fails or a repo has neither file, note
it honestly rather than dropping the repo.
## Phase 3 — Synthesize (one report)
## Phase 3 — Synthesize (one report → STATUS.md + inline)
Present ONE report in the chat. Default to showing it inline; if the user wants a tracked
snapshot they can diff over time (like `EVALUATION.md`), offer to write it to
`~/Projects/standards/STATUS.md` — their call, and don't commit it yourself.
Produce ONE report. **Write it to `~/Projects/standards/STATUS.md`**, overwriting the
previous snapshot, **and** show the same report inline in the chat — the file is the durable,
diffable record; the inline copy is for reading right now. Title it with today's date (run
`date +%F`).
Structure:
Structure (used identically for the file and the inline copy):
```
# Roundup — <date>
@@ -73,9 +74,26 @@ The (new)/(new:name) inbox items — ideas awaiting the new-repo bootstrap.
Repos missing AGENTS.md or a Current state; stale-looking states; anything that blocked a reader.
```
## Phase 4 — Persist the snapshot
`STATUS.md` is only a *tracked* snapshot if it's committed — that's the whole point of the
file (a dated history you can diff over time). So after writing it, commit and push **only
that file** to the standards repo, without asking (the same durability reflex as `/capture`):
- `git -C ~/Projects/standards add STATUS.md`
- `git -C ~/Projects/standards commit -m "Roundup snapshot — <date>" -- STATUS.md`
(the `-- STATUS.md` pathspec commits only the snapshot — never sweep unrelated standards
changes into a roundup commit)
- `git -C ~/Projects/standards push` (only if a remote is configured; if the push fails,
report it but don't treat the snapshot as lost — it's committed locally)
This write-and-commit of `STATUS.md` is the *only* thing `/roundup` changes on disk;
everything else — every project repo, every other file — stays strictly read-only.
## Rules
- Read-only. The only file you may write is `STATUS.md`, and only if the user asks for it.
- The only file you may write or commit is `~/Projects/standards/STATUS.md` (the snapshot).
Every project repo and every other file stays strictly read-only — never edit or commit them.
- Quote priorities and states as found; never re-rank projects or recommend what to do next
unprompted — that's the user's call.
- Preserve every item; if you can't place one, list it under "needs triage" rather than