Historical change record. The September 11 application-wide shutdown and its blanket resumption restrictions were superseded by the operator on September 15. This page records past actions and results; it does not impose current execution restrictions. See the stop-scope recovery record.
The operator explicitly requested updating the requirement and implementing development as the default working branch for all current and future repositories. EventHorizon issue 1577 planning had targeted main despite the intended supervised dev/test run. No Sleep worker was started. General automation remains paused. This engine administrator repair does not authorize managed-product production promotion.
Requirement checkpoint ee748720 corrected REQ-0003 before implementation. Initial PR 4402 merged as 608c85dc. Live migration exposed an unnecessary dependency on changing providers' administrative default settings. Service credentials can perform development work but cannot change those settings. Follow-up PR 4404, merged d995d7b1f1ba0ca4f41d58a85e4afba05df07a7e, removes that dependency. CodeCartography chooses the configured working branch directly, with no grant of administrator permissions to agents.
Requirements reads and ordinary issue workflows resolve the configured development branch, normally dev, regardless of the viewed branch or provider administrative default. API branch verification uses the requesting user's existing authorized credential. Native admission, worker execution and merge continuation recheck branch policy. Obsolete queued bases are retained for replan rather than executed against production. Onboarding and the one-shot migration share branch creation and capability reconciliation. Existing development refs, explicit exclusions and confirmed read-only restrictions remain intact. Empty repositories receive only an empty .gitkeep initial commit; no product requirements are invented.
reconcile-development-branches-once previews all enrolled projects. --execute saves reconciliation without starting agents, normal automation or delivery. Unavailable members and individual provider failures must be inspected; exit success is not proof all members are executable.
All ten managed Gitea repositories now have actual dev refs. Existing source refs were verified unchanged using authenticated Git. Existing Azure members already have development refs; final engine reconciliation and live API checks are pending below. Workflow triggers were audited before branch writes; no managed-product production push trigger on dev was observed.
Runtime Gitea identity discovers only three of the ten enrolled repositories. The operator credential performed branch setup for the other seven without changing worker membership or permissions. Azure BackupAndDisasterRecovery has a pre-existing permission-reconciliation 403; its read-only state is retained. These limits do not justify granting agents repository-administrator rights.
PokerStar and PokerCardEvaluator had stale administrative defaults pointing at nonexistent main. Their original master revisions were preserved and used for dev. PokerStar also contained an empty HEAD.lock dated 2025-09-24; no Git process was running. The single stale temporary lock was removed before repairing the invalid defaults. Both repositories lacked Gitea's generated Git hooks, causing successful branch creation in Git without branch-index updates. Only the missing pre-receive/update/post-receive generated hooks were restored from the active same-version Gitea templates; samples and existing information were preserved. Gitea's branch table was inspected and the two absent dev metadata rows were inserted transactionally from the matching verified master metadata. No existing rows or refs were replaced. Subsequent branch API reads return the exact dev revisions. ProfileBackups/julian and AI_Libraries/document-intelligence were genuinely empty and received only initial empty .gitkeep commits.
Final full Rust suite passed: 414 library, 1278 main, 87 Gitea, 16 Kubernetes tests, plus one subprocess test. Isolated PostgreSQL checks passed for custom development names, read-only authority, missing enrollment, conflicting policy and production rejection. HTTP tests cover creation and preservation of independently advanced refs on replay.
Final exact image is building. Backend still runs the previous revision in server-only mode; idle supervised pod currently has the initial branch-policy image. Final reconciliation, deployment and live requirements/default-picker verification remain pending. Sleep planning remains queued and unexecuted on its old base; pending acceptance for 1571 and 1447 is preserved.
Evidence owner: current administrator repair. Files under /home/ax_julian/temp/development-branch-migration/ preserve source-ref baselines, task/issue baselines, initial and final builds, and migration reports. Cleanup review 2026-09-22. No branch deletion or history rewrite was performed.
Final backend revision d995d7b1f1ba0ca4f41d58a85e4afba05df07a7e is deployed at generation 2390, immutable image digest sha256:62a56bd9482ff298d993c679b1b0b7095d7c4d3d533e59adc1f75913201a5760. Exact rollout and deployment receipt passed. Idle supervised worker has the same image and remains a sleep process. The previous backend image sha-b00e0fe6f066 is recorded for rollback.
Final shared engine reconciliation confirms dev exists for all 15 Azure repositories and the three service-accessible Gitea repositories. Administrator verification confirms Git refs and Gitea branch APIs agree for all ten managed Gitea repositories. Existing source history is preserved; AutoCoder main/dev advanced through the authorized engine repair merge. Seven other Gitea members retain their existing unavailable service-credential status; Azure BackupAndDisasterRecovery remains permission-blocked/read-only. These are existing execution-access limits, not permission grants made by this migration.
Actual authenticated application API checks passed for all 25 members: requirements resolve to dev even when the caller requests/views main. Existing native requirements content matches the remote dev artifact; repositories without requirements remain without invented content. The actual EventHorizon browser workspace selects dev, returns dev requirements, and displays the normal Issues view without browser errors. No debug page was added.
Post-deployment preservation checks passed: all nine protected issue rows byte-equivalent, both queued task records unchanged, zero running workers, backend still server-only. Sleep 1577 has not run; its old main-based planning task needs an explicit supervised replan against dev before execution. User acceptance for 1571 and 1447 remains pending. This change does not claim any gameplay fix or production application promotion.
Evidence: final/{build-metadata.json,rollout.json,migration-execute.log,api-verification.json,ui-verification.json,preservation-verification.json} and parent gitea-final-verification.json. Temporary authenticated sessions were revoked; isolated builder and temporary registry credentials were removed. Source worktree is clean. Verification complete for the development-branch policy; ordinary automation remains paused.