Correction to my previous comment: the rule is broader than "repos with no .dockerignore", and as stated it would give managers of already-canonical repos a false all-clear.
From the…
Review of a6a306d: PASS (merge-ready)
Third independent review, in a throwaway worktree. I did not author this change and did not perform either previous review; I re-derived every conclusio…
Blocked on #23 — do not land the .dockerignore portion of this issue
first.
Adding .claude/ to .dockerignore removes a live source of build-context
churn. .claude/worktrees/ is…
Ordering dependency: land this issue before the .dockerignore changes in
#8, and re-verify this issue's behaviour afterwards.
A fleet-wide warning came in saying that repos with no…
Verification summary
Single commit 02b63a4, branch fix/99-server-timeouts, based on origin/main at 9347a28. TODO.md is in the same commit as the work.
What changed
- `internal/s…
Summary of what landed here, in commit dcf3dd3:
internal/vaultik/vaultik.go— theVaultik.UIfield comment now namesUI.SetQuiet(true)as the actual mechanism, lists the seven message…
ORDERING HAZARD: this issue must not land in a consuming repo before #26 does. Adding the canonical .dockerignore can turn a currently-safe repo into a reliably false-green one.
Found by…
Manager notes: merge-ready re-confirmed against a fully uncached build.
No change to the label or assignment.
A fleet-wide warning came in that script/cibuild can report a green it…
Implementation plan
Read the C reference first (git show origin/c-master: on main.c, mdport.c,
mach_dep.c, save.c, rip.c). Two corrections to the issue's premise, both of
which…