grant/recap-relay
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct agent-doc accuracy: full /admin route list, git-state precision

Browse Source 
AGENTS.md: append four real /admin routes the list omitted (job-output/:id, output-store-ids, settings/promote-prompt, test-run-suite); replace the stale HEAD hash with 'last code commit is v0.2.11, docs-only commits on top'. ROADMAP.md: fix the untracked count + HEAD wording; drop the two now-resolved doc-precision follow-ups.
This commit is contained in:
Keysat
2026-06-13 12:02:36 -05:00
parent 7e5a7e3b7e
commit 87227a7ca6
2 changed files with 3 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ROADMAP.md
+1 -6
View File
@@ -4,7 +4,7 @@ Longer-term backlog for the relay. Near-term in-flight work + known box/local st
## Highest priority — commit the uncommitted working tree (git is at v0.2.11)
Versions are reconciled: box and local working tree are both at **0.2.124** (a concurrent 2026-06-13 session bumped 0.2.117→0.2.124 and shipped it). But committed git HEAD is still **v0.2.11** — everything since is uncommitted (≈28 modified + 153 untracked: v0.2.12→v0.2.124, the whole `internal-meetings` feature, diarization, `meeting-speaker-edits.js`, billing). This is the actual "catch up local git" task.
Versions are reconciled: box and local working tree are both at **0.2.124** (a concurrent 2026-06-13 session bumped 0.2.117→0.2.124 and shipped it). But the last committed **code** is still **v0.2.11** (only docs-only commits sit on top) — everything since is uncommitted (≈28 modified + ~150 untracked: v0.2.12→v0.2.124, the whole `internal-meetings` feature, diarization, `meeting-speaker-edits.js`, billing). This is the actual "catch up local git" task.
1. **Coordinate first** — confirm no other chat session is mid-edit on this tree before committing (the 117→124 files appeared mid-session from a parallel session).
2. **Decide commit granularity** — one big "catch up to 0.2.124" commit vs. logical chunks (internal-meetings / diarization / speaker-edit tools / billing). The history jump is large either way since nothing between v0.2.11 and v0.2.124 was committed.
@@ -19,11 +19,6 @@ Versions are reconciled: box and local working tree are both at **0.2.124** (a c
- **Make re-polish async for long meetings.** `POST /:id/repolish` is synchronous (one LLM pass per analysis window); a 2-hr meeting could make the request hang. Move to the existing job system (createJob/appendEvent/markComplete) + poll, like the main pipeline.
- **Speaker MERGE provenance.** Merge sums stats and approximates `chunks_appeared_in` as `max` (raw per-cluster chunk sets aren't retained). Recompute exactly from `rec.diarization` if precision ever matters.
## Doc precision follow-ups
- **`AGENTS.md` `## Current state` working-tree counts drift.** Reviewer caught `28 M` → actual `29 M` (and `183 total` → `184 total`) within minutes of writing the snapshot. Either refresh on every touch or change the phrasing to "(as of this write)" so the numbers stop reading as authoritative-forever.
- **`AGENTS.md` `### /admin/*` route list is non-exhaustive.** The brace-expanded shortlist silently omits at least three real routes registered in `server/routes/admin.js`: `GET /admin/job-output/:id` (line 268), `GET /admin/output-store-ids` (line 336), and `POST /admin/settings/promote-prompt` (line 1156). Either append them or label the list "(representative, not exhaustive)".
## Open issues (see docs/issues-backlog.md)
- **Empty analysis section at a window boundary** (observed v0.2.77 smoke test). Likely the LLM returning an empty `{title:"",summary:""}` section the stitcher accepts, or a window-merge boundary hole. Low priority. Full triage path in `docs/issues-backlog.md`.