Append-only record of material repository work. Each entry includes a timestamp, agent identity, task reference, evidence, and next action. Never record secrets.
- Task:
f6ccf7d5-9d97-4e1d-b1b6-3de273b56616; source task:e2546cbc-489c-44a1-9a91-7994abf0382f. - Created the isolated worktree on
fix/f6ccf7d5-task-list-resolutionfrom currentorigin/main(912706df). - Verification:
repos worktree add,repos scan, and clean worktree status all returnedrc=0. - Next: reproduce the task-list UUID and scoped-slug failures, then add the narrowest failing regression before production changes.
- Task:
f6ccf7d5-9d97-4e1d-b1b6-3de273b56616. - Confirmed the production-shaped cause: the Swiss task list is globally stored
with
project_id: null, while its project owns the same canonical slug inproject.task_list_id; the cloud resolver filters by project before matching. - Verification: the new focused regression returned
rc=1with literal output0 pass,2 fail, covering exact UUID and project canonical slug. - Next: teach the shared cloud resolver to validate the canonical legacy project/list link without allowing cross-project UUID attachment.
- Task:
f6ccf7d5-9d97-4e1d-b1b6-3de273b56616. - Updated the shared cloud task-list resolver to follow only the explicit
project.task_list_id === task_list.sluglegacy ownership link, with a negative control that rejects unrelated global lists. - Verification: resolver file
94 pass, 0 fail; cloud CLI list-routing file33 pass, 0 fail; TypeScript gaterc=0. - Real acceptance: the worktree CLI updated source task
e2546cbc-489c-44a1-9a91-7994abf0382fby both the exact UUID and canonical slug atrc=0; finaltask_list_idis09dc7e1d-7c20-4a52-b4fb-7675d7202f90. - Next: run full repository tests/build, staged secret scan, commit, push, and open the unmerged review PR.
- Task:
f6ccf7d5-9d97-4e1d-b1b6-3de273b56616. - Repository validation passed: full suite
3433 pass, 0 failacross 267 files; no-cloud boundary36 pass, 0 fail; typecheck and production build both returnedrc=0. - Acceptance remains live: source task
e2546cbc-489c-44a1-9a91-7994abf0382fresolves and stores the Swiss task-list UUID through both exact UUID and canonical-slug inputs. - Next: stage the exact candidate, run
shield review, commit with the requiredAgent: Quintiliantrailer, push, and open the unmerged pull request.
- Task:
409db44f-3300-4774-a001-602ff5443d64; added guarded existing-plan project linkage across SQLite and PostgreSQL storage, authenticated v1 HTTP, generated SDK, and local/cloud CLI paths. - The apply path uses exact plan, project, and sorted member-task revisions; immutable idempotent receipts and conditional rollback preserve prior links, while future plan members inherit the authoritative project and conflicting membership writes fail closed.
- Verification: focused linkage/storage/HTTP/OpenAPI/CLI gate
130 pass, 0 fail; typecheckrc=0; production build and no-cloud boundaryrc=0. The full repository suite reported3497 pass, 50 skip, 1 fail; its sole failure is the separately tracked ambient/tmp/node_modulesserver-bundle resolver defect, not a changed linkage lane. - Test isolation was repaired to use an explicit in-memory database. Incident
679082preserved a redacted exact fixture snapshot in task commente1b0546b-ff69-492c-b4cb-acea95d8dd8f; the 12 station02-local fixture objects were removed through supported CLI commands, all negative readbacks passed, and unrelated local plus hosted Dubai controls remained present. - Next: stage the exact candidate, run
shield review, commit once with the requiredAgent: Theophrastustrailer, push, and open the draft pull request.
- Task:
93cfec1f-063c-44dd-a0e8-f50ad00836f8; reproduced the hostedlink-reffalse success where POST exited 0 with a complete-looking row but immediate reverse and task readback exposed no ref. - The CLI now requires the advertised task-read, task-write, and reverse-read contract before mutation, strictly validates response envelopes, and emits success only after both authoritative read paths return the exact row. OpenAPI and the generated SDK now advertise the existing server routes.
- Verification so far: focused two-sided regression
5 pass, 0 fail, TypeScriptrc=0, production buildrc=0, package dry-runrc=0. Against the current hosted authority, the fixed source command exits 1 withREMOTE_GIT_REF_UNSUPPORTEDbefore mutation instead of printing success. - Next: finish the affected and full Bun suites, stage and scan the exact
candidate, commit with
Agent: vitruvius, push, and open the unmerged pull request for independent review.
- Task:
93cfec1f-063c-44dd-a0e8-f50ad00836f8; current base remainsorigin/mainata73c219. - Affected CLI/server/OpenAPI validation passed
153 pass, 0 fail; no-cloud passed36 pass, 1 skip, 0 fail; typecheck, production build, and package dry-run returnedrc=0. - The repository-wide suite reached
3556 pass, 63 skip, 10 fail; all ten failures were current-authority detail fixtures missing the newly advertised ref-read routes. After fixture-only remediation, the five affected files and direct regression passed33 pass, 0 fail. - Real hosted controls now fail
link-refandfind-refbefore mutation withREMOTE_GIT_REF_UNSUPPORTED; task detail remains available and reportsgit_refs: nullwith an explicit warning instead of a false empty set. - Next: stage the exact candidate, run the staged security scan, commit once, push, and open the unmerged pull request for the fixed fabricius review.