4 Commits

Include renames

Author	SHA1	Message	Date
Nick	4eefc15837	fix(lifecycle+auth): canonical gitea auth path, terminalization helper, fault-injection gaps (T15 Parts A-E) ... - scripts/gitea_auth.py: single credential ladder (env -> 0600 token file -> git credential fill); 6 consumers migrated off direct os.environ reads - rune_operator: consolidate 5 duplicated failure blocks into _terminalize_execution_failure; fix 3 fault-injection gaps: (1) dual-module PreparedTool identity split crashed approval-path saves, (2) fallback-model failure escaped send_task (created/pending orphan), (3) running-transition save uncaught (running-with-no-owner) - envelope task.status now agrees with canonical ledger (awaiting_approval) - orphan task_ac35f4e287c8 terminalized failed with durable evidence - tests: gitea auth ladder (6), lifecycle fault matrix (9 boundaries + restart/reload + helper contract); 1280 green in ci-venv; ratchet 352/80	2026-09-11 20:15:57 +01:00
Nick	82bd50f410	fix(pipeline): send release-drift label as integer IDs, not names (#192) ... Quality-gate finding 6: POST /issues 'labels' requires integer IDs in Gitea; the script sent the label NAME string, so the label never attached. Label names are now resolved server-side via GET /labels (repo convention per shared/custodian.py), created when missing, and skipped — issue still files — when resolution and creation both fail. main() gains an injectable api client so the flow is testable with a fake API. Red evidence: 3 fake-client tests failed against the pre-fix code (network URLError — no injectable seam; name-string payload). Green: 13/13.	2026-09-07 15:00:53 +01:00
Nick	a7b9639a2e	fix(pipeline): report version-behind-tag as drift with an anomaly flag (#192) ... Spec-gate finding 3: assemble_release_decision returned converged=True when master's __version__ was BELOW the latest tag — silent convergence for a state that is drift (a bump merged without riding a release, or a tag moved backwards). The decision now returns converged=False, warranted_bump=None (the net must not act: bumping master cannot converge with a tag already ahead) and a new 'anomaly': 'version_behind_tag' field (None otherwise). The maintenance reconciler files the issue as before (DRIFT=true) and the issue body now flags the anomaly explicitly. Red evidence: 2 new decision tests failed with converged=True; the drift-body anomaly-flag test failed; real-repo tag-ahead test added. Green: 91/91 across convergence, drift-issue, and contract tests.	2026-09-07 14:29:02 +01:00
Nick	98afcd7ded	feat(pipeline): maintenance drift reconciliation (#192)	2026-09-07 12:19:30 +01:00