You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Housekeeping that came out of the 2026-09-07 parity sweep. Individually trivial, collectively worth one PR.
1. Fold the parity re-measure into work-consolidation.md
docs/parity-refresh-2026-09 carries one unmerged commit (cc57a46) that:
corrects the AI provisioning model (no user API key — the single most important correction in that revision)
reconciles the doc with what actually merged (§1c verb defects and G15–G20 were still listed as open)
records the real test baseline
adds §1e for the 2026-09-06 account-cluster sweep
Until it merges, the master planning doc contradicts the code on dev. Merge it, then update it again with the findings from this sweep (see item 2).
⚠️work-consolidation.md is edited by several concurrent sessions. Merge it on its own, not bundled into a feature PR.
2. Record the 2026-09-07 findings in the master doc
New facts this sweep established that are not yet written down anywhere:
The live spec is now 228 paths / 296 operations (was 226/294 on 2026-09-05); the client builds ~180 request builders covering ~150 distinct operations.
accountStatus exists on the User schema and is unmodelled by the client — filed as its own issue.
45 operations are x-auth-type: session and reject Bearer. The ones that matter: invite/share claim, send-verification-email, user/engagement, dashboard-layout, front-wall-layout, and every widgets/* route. This makes the dashboard work backend-blocked, not merely undecided.
The message permalink shape in MessagePermalink is wrong — /messages/{id} redirects to /login; the public form is /user/{username}/status/{id}.
GET /api/github/orgs returns a bare array, not the usual {message?, <resource>} envelope.
3. Reconcile docs/api-coverage.md
The matrix was last audited 2026-09-05 at 187 rows. Since then PR #24, #25, #30, #31, #32, #33, #34 landed. Re-score it, and add rows for anything this sweep surfaced that it does not carry (/api/folders, /api/users/{username}/documents, /api/auth/github/status, /api/github/orgs, accountStatus).
Record x-auth-type per row while you are in there — "the client cannot reach this under Bearer" is coverage information the matrix currently has no column for, and it is the difference between "not built" and "not buildable".
4. Prune stale worktrees
Ten worktrees exist under .claude/worktrees/; most are for branches already merged:
Remove the ones whose branches are merged. ⚠️Check git status in each first — a concurrent session may be working in one, and removing a worktree with uncommitted changes loses them. Leave parity-refresh alone until item 1 is done.
5. Local dev is behind origin/dev
The local dev branch sits at 562ed8e; origin/dev is at 42a63ff with PRs #32, #33, #34 merged. Fast-forward before starting any work, or a new branch will be cut from a stale base.
6. Issues #27, #28, #29 were closed on 2026-09-07 — one caveat
Summary
Housekeeping that came out of the 2026-09-07 parity sweep. Individually trivial, collectively worth one PR.
1. Fold the parity re-measure into
work-consolidation.mddocs/parity-refresh-2026-09carries one unmerged commit (cc57a46) that:Until it merges, the master planning doc contradicts the code on
dev. Merge it, then update it again with the findings from this sweep (see item 2).work-consolidation.mdis edited by several concurrent sessions. Merge it on its own, not bundled into a feature PR.2. Record the 2026-09-07 findings in the master doc
New facts this sweep established that are not yet written down anywhere:
accountStatusexists on the User schema and is unmodelled by the client — filed as its own issue.x-auth-type: sessionand reject Bearer. The ones that matter: invite/share claim,send-verification-email,user/engagement,dashboard-layout,front-wall-layout, and everywidgets/*route. This makes the dashboard work backend-blocked, not merely undecided./api/folders, 4 ops) despite being removed from macOS in PR refactor(lists): remove the List Folders feature, keep parent/child list nesting #19.MessagePermalinkis wrong —/messages/{id}redirects to/login; the public form is/user/{username}/status/{id}.GET /api/github/orgsreturns a bare array, not the usual{message?, <resource>}envelope.3. Reconcile
docs/api-coverage.mdThe matrix was last audited 2026-09-05 at 187 rows. Since then PR #24, #25, #30, #31, #32, #33, #34 landed. Re-score it, and add rows for anything this sweep surfaced that it does not carry (
/api/folders,/api/users/{username}/documents,/api/auth/github/status,/api/github/orgs,accountStatus).Record
x-auth-typeper row while you are in there — "the client cannot reach this under Bearer" is coverage information the matrix currently has no column for, and it is the difference between "not built" and "not buildable".4. Prune stale worktrees
Ten worktrees exist under
.claude/worktrees/; most are for branches already merged:Remove the ones whose branches are merged.⚠️ Check
git statusin each first — a concurrent session may be working in one, and removing a worktree with uncommitted changes loses them. Leaveparity-refreshalone until item 1 is done.5. Local
devis behindorigin/devThe local
devbranch sits at562ed8e;origin/devis at42a63ffwith PRs #32, #33, #34 merged. Fast-forward before starting any work, or a new branch will be cut from a stale base.6. Issues #27, #28, #29 were closed on 2026-09-07 — one caveat
/login, and "Get embed code" was never built; both are now tracked in their own issue. Closing Message Features Need Implemented #27 was right — just make sure the remainder is not assumed shipped along with it.No action needed here; recorded so the next sweep does not re-derive it.
Acceptance criteria
origin/dev.docs/api-coverage.mdreflects every merged PR and carries auth-type information.Notes
Docs work has its own gate:
.claude/skills/doc-engineer/assets/docs-quality-checklist.md.