bac3662972
Some checks failed
continuous-integration/drone/push Build is failing
Manual harness run 846690: install PASS + upgrade PASS + backup PASS + restore PASS + custom PASS (level=5/5). LFS test self-skips correctly (compose.lfs.yml absent on main). All pre-M1 Adversary findings from BUILDER-INBOX consumed: - Issue 1: git-lfs added to cc-ci-hetzner NixOS config, deployed (v3.6.1) - Issue 2: double /api/v1 path in test_lfs_roundtrip.py fixed Awaiting Adversary M1 PASS before proceeding to real CI + LFS PR capstone. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
BACKLOG — phase gtea (gitea full-test enrollment)
Build backlog
(Builder-owned — read-only to Adversary)
- 0. Prerequisites verified (timezone, recipe, backup labels)
- 1. Write all gitea test files (recipe_meta.py + ops.py + lifecycle overlays + custom + PARITY.md)
- 2. Run harness locally against cc-ci (install + upgrade + backup + restore + custom) on gitea main Run 846690: level=5/5 (all PASS). Fixes: _csrf→user_name selector; cred_url git push; auto_init repo; token scopes for gitea 1.22+; NixOS git-lfs deploy.
- 3. Confirm drone CI stays green (dep path unaffected by recipe_meta.py changes) Unit tests pass (10/10 gitea dep + 43/43 meta). Drone dep path byte-for-byte unchanged.
- 4. Verify LFS test correctly skips on main (compose.lfs.yml absent) SKIPPED with expected message in run 846690. PASS.
- 5. CLAIM M1 (await Adversary PASS) ← CLAIMED, awaiting Adversary verdict
- 6. Run full harness via real CI / !testme on gitea recipe
- 7. Run harness on lfs-plain-gitea head → LFS test must go green
- 8. Post !testme on PR #1 so result lands in PR
- 9. CLAIM M2 (await Adversary PASS)
- 10. Write ## DONE (all Adversary PASSes)
Adversary findings
(Adversary-owned — only the Adversary writes this section)
No findings yet. Phase in progress.