Repository branch hygiene and post-0.5.37 cleanup

[ByBrawe]

Tracks repository cleanup after the 0.5.36/0.5.37 long-session reliability releases.

• Classify stale branches as merged, superseded, diagnostic/probe, release, or active.
• Remove obsolete merged fix/release branches after PR/SHA verification via Automate safe merged-branch cleanup #158.
• Preserve inactive unique branch tips in archive/legacy-branches-2026-09-21 with an exact branch-name → SHA manifest, then retire the original refs via Archive and retire inactive legacy branches #159.
• Preserve OpenCode 2/runtime-contract evidence in the archive rather than deleting the underlying commit tips.
• Verify cleanup keeps current main/release behavior and scheduled latest-Goal coexistence coverage intact.
• Keep future branch debt bounded with main-push Branch Hygiene: PR dry-run is read-only; cleanup deletes only exact merged heads or exact manifest-backed archived heads after ref revalidation.

Final repository shape after cleanup: main plus the permanent recovery archive ref. Release 0.5.38 is published; the archive keeps every retired legacy branch tip recoverable.

[ByBrawe]

Branch cleanup manifest (2026-09-20)

Repository: ByBrawe/opencode-loop

• non-main branches: 221
• active/open-PR heads to KEEP: 0
• Wave A: merged-PR heads with no V2/probe/diagnostic marker: 78
• Wave B: explicit no-PR disposable/release/tmp branches with no V2 marker: 5
• HOLD for evidence review (V2/opencode2/probe/diag/experimental/etc.): 107

Wave A — delete after final spot-check

• chore/community-regressions-goal-readme
• chore/release-automation
• chore/sync-modularized-bundle
• ci/artifact-build
• ci/bootstrap-readiness
• ci/verify-npm-publish
• compat-host-check
• copilot/fix-plugin-load-silently
• docs/goal-mode-headline
• docs/prefer-opencode-goal-0.5.25
• feat/goal-companion-updater
• fix-compaction-test-wait
• fix/dedicated-goal-tool-isolation
• fix/empty-assistant-turn-loop
• fix/goal-canary-bootstrap-retry
• fix/idle-loop-scheduling
• fix/installer-command-clutter
• fix/loop-goal-user-steering
• fix/network-recovery-terminal-guard
• fix/no-now-first-run-delay
• fix/npm-publish-propagation
• fix/release-snapshot-checkout
• fix/run-now-target-parity
• fix/stable-loop-now-target
• fix/stable-status-no-now-due
• fix/state-write-retry-hardening
• fix/v0.5.23-dispatch-recovery
• fix/v0.5.24-native-compaction-status
• pack-script-adjustment
• refactor-command-lifecycle-v1
• refactor-command-router-20260814
• refactor-compaction-runtime-20260814
• refactor-executor-runtime-20260814
• refactor-goal-command-handlers-20260814
• refactor-goal-lifecycle-20260814
• refactor-goal-policy-20260814
• refactor-goal-support-20260814
• refactor-host-runtime-v1
• refactor-job-workspace-20260814
• refactor-loop-command-handlers-20260814
• refactor-loop-jobs-clean
• refactor-loop-process
• refactor-loop-registration-20260814
• refactor-message-runtime-v1
• refactor-scheduler-runtime-20260814
• refactor-session-activity-20260814
• refactor-session-status-20260814
• refactor/bundle-gate
• refactor/executor-action-dispatch
• refactor/goal-evidence-runtime
• refactor/goal-presentation-runtime
• refactor/plugin-build-command
• refactor/run-admission-runtime
• refactor/run-finalization-runtime
• refactor/source-module-entry
• refactor/v1-entrypoint-safe
• release-prep-0.5.28-current
• release-prep-workflow
• release/0.5.28-metadata
• release/0.5.34-prep
• release/0.5.35-prep
• release/prepare-v0.5.29
• release/prepare-v0.5.30
• release/prepare-v0.5.31
• release/prepare-v0.5.32
• release/prepare-v0.5.33
• release/prepare-v0.5.36
• release/prepare-v0.5.37
• release/v0.5.21-opencode-1.18
• release/v0.5.22-compat-hardening
• runtime-event-observer
• runtime-lifecycle-contract
• test-comprehensive-watchdog
• test/current-goal-coexistence
• test/goal-host-bootstrap-hardening
• test/latest-goal-coexistence-scheduled
• test/loop-goal-queued-steering-host
• test/stable-loop-now-real-host

Wave B — explicit disposable/no-PR candidates

• merge47
• release-prep-0.5.28-final
• release/0.5.29-metadata
• release/npm-v0.5.28
• release/npm-v0.5.34

HOLD — evidence review before deletion

Not listed individually here to keep the issue readable. These are deliberately excluded from automated cleanup until their unique evidence is confirmed preserved in PR/issue history.

Deletion has NOT been executed by this connector; it exposes branch read/update but no delete-ref action.

[ByBrawe]

Branch-hygiene follow-up:

• Repository setting delete_branch_on_merge is currently false.
• Enabling GitHub's repository-level automatic head-branch deletion is the preferred prevention mechanism.
• For Goal specifically, do not implement branch deletion through GitHub Actions: scripts/actions-security-gate.mjs intentionally requires read-only contents permissions and forbids workflow/API write mutations. Weakening that policy just to clean branches would regress the repository's security boundary.
• The connected GitHub API surface available in this maintenance session can read/create/update refs but does not expose delete-ref or repository-settings mutation, so the existing cleanup manifest is prepared but branch deletion itself has not been executed here.

[ByBrawe]

Repository-level prevention command for an admin-authenticated GitHub CLI session:

gh repo edit ByBrawe/opencode-loop --delete-branch-on-merge

Current repository metadata reports delete_branch_on_merge=false; enabling this setting prevents future merged PR head accumulation.

[ByBrawe]

V2/diagnostic HOLD refinement:

• merged PR heads with V2/probe markers: 25 — safe cleanup candidates because their PR/diff history is already preserved.
• closed-unmerged V2/probe heads: 29 — HOLD until evidence is summarized or superseded.
• V2/probe branches with no PR record: 53 — HOLD; highest unique-evidence risk.

Merged V2/probe cleanup candidates:

• feat-v2-action-runtime-20260814
• feat-v2-interval-runtime-20260814
• feat/v2-loop-doctor
• feat/v2-loop-export
• feat/v2-loop-help
• feat/v2-loop-logs
• fix/v2-command-transport-current
• test-host-adapter-contract
• test/v2-real-control-lifecycle
• test/v2-real-loop-canary-current
• v2-activation-proof
• v2-context-integration-clean
• v2-control-commands-20260814
• v2-event-normalizer
• v2-lifecycle-ready
• v2-loop-status-parity
• v2-plugin-sentinel
• v2-prompt-slice-current
• v2-prompt-wiring-20260814
• v2-runtime-factory
• v2-runtime-host-cleanup
• v2-runtime-scope
• v2-session-registry
• v2-session-runtime-manager
• v2-setup-loader

[ByBrawe]

New long-session failure found from the 2026-09-21 Loto Diyarı export/screenshots and now tracked by PR #153.

Evidence from the persisted Loop job after the provider failure:

• runCount: 42
• enabled: true
• paused: false
• failureCount: 0
• infrastructureFailureCount: 0

The UI showed a terminal provider/session failure (OpenCode's free tier can only be used from within OpenCode), but stable V1 ignored raw session.error and later idle/stale recovery could release the run without recording the terminal failure. The supplied loop log also showed heavy duplicate stale-recovery diagnostics from concurrent status probes.

PR #153:

• routes Loop-owned session.error into the executor;
• pauses fail-closed on terminal non-retryable/auth/policy/unknown errors;
• refunds + backs off retryable terminal API errors;
• leaves MessageAbortedError on existing abort semantics;
• deduplicates identical recovery diagnostics per active run;
• adds exact free-tier-message and concurrent-log regressions;
• keeps modular source and single-file Bun bundle synchronized.

The first feature head passed general CI, V2 lifecycle and dedicated Goal coexistence; Bundle Gate initially failed only because the committed generated bundle was intentionally not yet regenerated. The exact Bun-generated diff was applied, and the bundle gate then passed. A pre-existing Windows temp-directory EBUSY flake was also hardened with bounded fs.rm retries on the current head.

[ByBrawe]

Loto reliability follow-up:

• Pause Loop on terminal OpenCode session errors #153 (terminal OpenCode session-error fail-safe + recovery-log dedupe) is merged into main at c37ed75.
• Pause repeated waiting-user continuations #154 is the second half of the same incident: plain continuation stays unlimited for normal work, but two consecutive explicit "waiting for user approval/access/action" assistant replies pause the job instead of polling the external dependency forever. The exact Turkish "Onay bekleyenler: commit + push, canlı migration, cihaz testi" wording from the session is covered by regression tests.
• 0.5.38 release preparation will start only after Pause repeated waiting-user continuations #154's exact head is green and merged, so both fixes ship together.

[ByBrawe]

Cleanup is complete. #158 removed exact merged heads; #159 preserved every remaining inactive branch tip under archive/legacy-branches-2026-09-21 with a branch→SHA manifest, then retired the original refs only after archive ancestry and live-ref SHA revalidation. Current repo shape is main + the permanent recovery archive ref, and Branch Hygiene keeps future merged/archive-backed debt bounded. Closing as completed.