claude@clouddev1
5f28de8ac3
main independently wrote its own docs/handoff/20260615-handoff-70.md the same day, so my global-sequence handoff-70 was an add/add conflict waiting to merge. Relocate it to docs/ci/handoff/20260615-handoff-ci-01.md (its own namespace, like docs/ci/adr) + a README index. main's handoff-70 is untouched; the merge becomes conflict-free.
1.1 KiB
1.1 KiB
CI / Build subproject — session handoffs
Handover notes for the CI / release pipeline work (the Gitea Actions
workflows under .gitea/, the nix flake, the release tooling). Kept in their
own namespace, separate from the project-wide session handoffs in
docs/handoff/, so a CI-branch handoff never competes with
main's global handoff sequence for numbers — the same split the CI ADRs use
(docs/ci/adr/). This is not hypothetical: main
independently wrote a handoff-70 the same day this subproject's first handoff
was drafted.
Numbering. Files are named <date>-handoff-ci-<NN>.md and referenced in
prose as handoff-ci-NN. Assign the next free NN from this index.
Index
- handoff-ci-01 — the CI/release pipeline build-out
— Gitea Actions gate (clippy + test) + a six-target release (four via
cargo-zigbuildon av*tag, two macOS via dispatch on a Tart runner), all on a nix flake; decisions indocs/ci/adr/. Built on thecibranch, mergedmainin, gate green (2488 tests), ready to promote tomain.