hygiene(tick-history): 2026-05-03T10:51Z — deferred-5-CI-ref'd-sh investigation

docs/hygiene-history/ticks/2026/05/03/1051Z.md

@@ -0,0 +1 @@
+| 2026-05-03T10:51:00Z | opus-4-7 / autonomous-loop continuation | a2e2cc3a | **Deferred-5-CI-ref'd-sh investigation: 3 workflows lack setup-bun; flag-compatibility check needed before .ts swap.** Step 0a 12 min approaching threshold — looking for real work continuously per Aaron's tick-15 corrective. Investigation: deferred 5 .sh files (audit-memory-index-duplicates, audit-memory-references, check-archive-header-section33, check-no-conflict-markers, check-tick-history-order) all referenced from 3 CI workflows: gate.yml + memory-index-duplicate-lint.yml + memory-reference-existence-lint.yml. **None have setup-bun step**. Switching .sh → .ts requires (1) add `oven-sh/setup-bun@v2` step before the lint step, (2) verify .ts equivalent supports same CLI flags (e.g., audit-memory-index-duplicates.sh runs with `--enforce` flag — need to verify .ts has same), (3) verify exit code parity, (4) test in CI before removing .sh. **Risk-stratification**: gate.yml is most-load-bearing (3 of 5 .sh refs); a broken edit blocks all PRs. The two memory-*-lint.yml workflows are scoped (path filters: only memory/MEMORY.md changes). Recommended sequence: (a) memory-index-duplicate-lint.yml first (lowest risk; single-tool workflow), (b) memory-reference-existence-lint.yml next, (c) gate.yml last (after first two prove the pattern). Each is its own bounded PR. Per careful-action discipline, none of these are bounded enough for current tick + risk profile too high for end-of-session. **CADENCE-TRACK**: AutoDream still overdue (last 2026-04-23, ~10 days); cadence-rule prohibits same-session run. Defer next-session unchanged. Today's session has produced 50+ PRs; the .sh→.ts conversion is the natural extension that completes Aaron's "fully converted" directive but at workflow-level granularity, not file-level. | All recent PRs (#1366-1375) MERGED; deferred 5 .sh CI-cleanup awaits dedicated bounded PRs (3 workflows, sequential) | This tick teaches **risk-stratified deferral discipline**: when a directive's remaining scope crosses load-bearing boundaries (gate.yml is the all-PR gate), defer to dedicated bounded PRs with sequenced rollout (low-risk → medium → high). Not all "cleanup" is mechanical; some is substantive infrastructure change. Future-Otto: when filing a multi-file cleanup PR, explicitly stratify by reference-type (zero-ref → workflow-ref → load-bearing-workflow-ref) and execute each stratum as separate bounded PR. |