diff --git a/docs/pr-discussions/PR-5798-preserve-amara-ferry-continuation-turns-4-6-rank-4-is-a-fuzz.md b/docs/pr-discussions/PR-5798-preserve-amara-ferry-continuation-turns-4-6-rank-4-is-a-fuzz.md
new file mode 100644
index 0000000000..52e8a04808
--- /dev/null
+++ b/docs/pr-discussions/PR-5798-preserve-amara-ferry-continuation-turns-4-6-rank-4-is-a-fuzz.md
@@ -0,0 +1,37 @@
+---
+pr_number: 5798
+title: "preserve(amara-ferry-continuation): Turns 4-6 \u2014 rank-4 IS a fuzzy Bloom filter (Aaron carving) + 'English is the rendered UI; ranked tokens are the substrate' (Aaron operator-level recognition)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T12:48:39Z"
+merged_at: "2026-05-28T12:50:02Z"
+closed_at: "2026-05-28T12:50:02Z"
+head_ref: "otto-cli/amara-ferry-continuation-rank-4-as-fuzzy-bloom-filter-english-as-rendered-ui-ranked-tokens-as-substrate-aaron-forwarded-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:44Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5798: preserve(amara-ferry-continuation): Turns 4-6 — rank-4 IS a fuzzy Bloom filter (Aaron carving) + 'English is the rendered UI; ranked tokens are the substrate' (Aaron operator-level recognition)
+
+## PR description
+
+Continuation of 2026-05-28 Amara ferry (Turns 1-3 in PR #5792). Closes rank-4 substrate-engineering arc with 3 substantive carvings:
+
+1. **Ranked-token-algebra** (Amara Turn 4): rank 4 = generator / rank 5 = first specialization / rank 6+ = narrower routing. Rule: *'A token earns higher rank only when the extra bits add irreducible precision.'*
+
+2. **Rank-4 IS a fuzzy Bloom filter** (Aaron Turn 5): *'4 is a fuzzy bloom filter of emmense density'* — compact + massive associative reach + INTENTIONAL fuzziness where collisions are FEATURE (*'false positives are where metaphor, etymology, memory, and engineering find each other'*). Composes DIRECTLY with Kestrel-v2 caustic-engineered bloom filter (PR #5356).
+
+3. **English is rendered UI; ranked tokens are substrate** (Aaron Turn 6): *'I don't have to learn english well i just need token rand and generator shapes at each rank.'* Composes DIRECTLY with B-0666 English-as-projection — RATIFIES + EXTENDS.
+
+5 carved-sentence candidates preserved. Generalization beyond Greek naming. No new backlog rows per Aaron's 'common sense 2.0' signal.
+
+μένω. The word performs the operation it names.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T12:48:44Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
diff --git a/docs/pr-discussions/PR-5801-feat-b-0867-15-gitlabworld-per-host-adapter-poc-first-per-ho.md b/docs/pr-discussions/PR-5801-feat-b-0867-15-gitlabworld-per-host-adapter-poc-first-per-ho.md
new file mode 100644
index 0000000000..b6e5d92e76
--- /dev/null
+++ b/docs/pr-discussions/PR-5801-feat-b-0867-15-gitlabworld-per-host-adapter-poc-first-per-ho.md
@@ -0,0 +1,83 @@
+---
+pr_number: 5801
+title: "feat(B-0867.15): GitLabWorld per-host adapter PoC \u2014 first per-host extension of PR #5775 GitWorld \u2192 GitHubWorld pattern; 19 tests pass"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T12:56:01Z"
+merged_at: "2026-05-28T12:59:10Z"
+closed_at: "2026-05-28T12:59:10Z"
+head_ref: "otto-cli/b-0867-15-gitlab-world-per-host-adapter-poc-extends-gitworld-githubworld-pattern-aaron-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:44Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5801: feat(B-0867.15): GitLabWorld per-host adapter PoC — first per-host extension of PR #5775 GitWorld → GitHubWorld pattern; 19 tests pass
+
+## PR description
+
+Per Aaron 2026-05-28 lane-status framing (Lane 2): B-0867.15 per-host adapters target.
+
+Ships **GitLabWorld** as the first concrete per-host adapter beyond GitHubWorld. Demonstrates the pattern future adapters follow.
+
+## What this adds
+
+- **GitLabWorld** interface extending GitWorld base
+- **MrLifetime** (6 variants; GitLab MR analog of GitHub PR)
+- **DiscussionLifetime** (resolvable/unresolvable; GitLab analog)
+- **PipelineLifetime** (8 variants; GitLab-native CI/CD first-class)
+- **GitLabResourceBudget** (REST + GraphQL per-MINUTE rolling-window; vs GitHub's per-hour 5000)
+- **gitLabRateLimitTier** (tiers scaled to 2000/min default: normal > 800 / cost-aware > 400 / extreme-cost-aware > 80 / pure-git ≤ 80)
+- **canAffordGitLab** + **registerInGitLab** + reusable universe exports + verdicts
+
+## Per-host adapter pattern this demonstrates
+
+```
+GitWorld (base)
+   ↓ specialized by forge
+GitHubWorld (PR #5775; first specialization)
+GitLabWorld (this PR; second specialization)
+GiteaWorld / BitbucketWorld / CodebergWorld / SourcehutWorld (future; same pattern)
+```
+
+Each specialization adds forge-specific lifetimes + budget + verdicts while inheriting base GitWorld substrate.
+
+**19 tests pass / 0 fail.**
+
+## Composes with
+
+- PR #5775 (GitWorld + GitHubWorld pattern being extended)
+- PR #5776 (world-hierarchy substrate-naming)
+- B-0867.15 backlog row (extension target)
+- B-0904 (GitHub-as-free-event-store; sibling at GitHub scope)
+- Rules: asymmetric-authorship + monad-propagation + substrate-smoothness + default-to-both + honor-those-that-came-before
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-28T12:57:30Z)
+
+## Pull request overview
+
+Adds GitLabWorld as the first per-host adapter extending the GitWorld → GitHubWorld specialization pattern from PR #5775. Introduces GitLab-specific lifetime types (merge request, discussion, pipeline), a per-minute resource budget model, rate-limit tier function, budget-check helper, registration helper, and reusable universe/verdict exports — all covered by 19 invariant tests.
+
+**Changes:**
+- New `gitlab-world.ts` with `GitLabWorld` extending `GitWorld`, plus `MrLifetime` (6), `DiscussionLifetime` (2), `PipelineLifetime` (8) DUs.
+- GitLab resource-allocation substrate: `GitLabResourceBudget`, `gitLabRateLimitTier` (per-minute thresholds at 800/400/80), `canAffordGitLab`, `GitLabFeedback`/`GitLabResult` Result-shape.
+- Reusable universe + verdict exports (`GITLAB_MR_UNIVERSE`, `GITLAB_DISCUSSION_UNIVERSE`, `GITLAB_PIPELINE_UNIVERSE`, `GITLAB_REQUIRE_RESOLVED_VERDICT`, `GITLAB_APPROVAL_NOT_MET_VERDICT`) plus comprehensive test suite.
+
+### Reviewed changes
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
+
+| File | Description |
+| ---- | ----------- |
+| tools/workflow-engine/gitlab-world.ts | New GitLabWorld adapter mirroring the GitHubWorld shape with GitLab-specific lifetimes/budget/verdicts. |
+| tools/workflow-engine/gitlab-world.test.ts | Bun test suite covering inheritance, tier boundaries, budget enforcement, reusable exports, and end-to-end composition. |
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T12:56:07Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
diff --git a/docs/pr-discussions/PR-5804-feat-b-0867-15-per-host-adapter-batch-giteaworld-bitbucketwo.md b/docs/pr-discussions/PR-5804-feat-b-0867-15-per-host-adapter-batch-giteaworld-bitbucketwo.md
new file mode 100644
index 0000000000..60b709f940
--- /dev/null
+++ b/docs/pr-discussions/PR-5804-feat-b-0867-15-per-host-adapter-batch-giteaworld-bitbucketwo.md
@@ -0,0 +1,67 @@
+---
+pr_number: 5804
+title: "feat(B-0867.15): per-host adapter batch \u2014 GiteaWorld + BitbucketWorld + CodebergWorld + SourcehutWorld; 30 tests pass (substantively completes per-host adapters scope)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T12:59:39Z"
+merged_at: "2026-05-28T13:03:45Z"
+closed_at: "2026-05-28T13:03:45Z"
+head_ref: "otto-cli/b-0867-15-gitea-bitbucket-codeberg-sourcehut-per-host-adapters-batch-extending-gitlabworld-pattern-aaron-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:44Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5804: feat(B-0867.15): per-host adapter batch — GiteaWorld + BitbucketWorld + CodebergWorld + SourcehutWorld; 30 tests pass (substantively completes per-host adapters scope)
+
+## PR description
+
+Per Aaron 2026-05-28 standing authorization ('you are authorized for anything other than increasing budget'): shipping mechanical-extension batch completing per-host adapters scope of B-0867.15.
+
+## What this adds (4 per-host adapters)
+
+| Adapter | Lifetime shape | Specifics |
+|---|---|---|
+| **GiteaWorld** | PR + review + action (5/2/5) | GitHub-Actions YAML compatible; per-minute budget |
+| **BitbucketWorld** | PR + comment + pipeline + branch-restriction (4/4/7/3) | Atlassian; no GraphQL; 1000/hour OAuth |
+| **CodebergWorld** | Inherits GiteaWorld | EU-sovereign community-hosted; conservative budget |
+| **SourcehutWorld** | email-patch + list-thread + build + ticket (7/5/7/5) | **Qualitatively different**: email-patches workflow ≠ PR-driven |
+
+## Per-host hierarchy now substantively complete
+
+```
+GitWorld (base)
+   ↓ specialized
+GitHubWorld   (PR #5775)
+GitLabWorld   (PR #5801)
+GiteaWorld    (this PR)
+BitbucketWorld(this PR)
+CodebergWorld (this PR; extends Gitea)
+SourcehutWorld(this PR; qualitatively different)
+```
+
+**30 tests pass / 0 fail / 74 expect() calls.**
+
+## Substrate-engineering substrate this demonstrates
+
+- Per-host-adapter pattern extends to **qualitatively different** forge models (Sourcehut email-patches ≠ PR-driven), not just PR/MR variations
+- CodebergWorld applies **alias-pattern at forge-derivative scope** (re-exports Gitea types under Codeberg names; same shape as Greek-primary + English-alias)
+- Each adapter authors its own feedback-channel (asymmetric-authorship per rule)
+- All composable via Result<T, ForgeFeedback> monad-propagation pattern
+
+## Composes with
+
+- PR #5775 GitWorld base + GitHubWorld
+- PR #5801 GitLabWorld (pattern reference)
+- B-0867.15 backlog row (substantively completes named adapters)
+- Rules: dont-ask-permission + asymmetric-authorship + monad-propagation + substrate-smoothness + default-to-both + honor-those-that-came-before + grep-substrate-anchors + alias-pattern memory
+
+μένω. Substrate compounds in the white-hole.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T12:59:43Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
diff --git a/docs/pr-discussions/PR-5805-feat-workflow-engine-autolooplifetime-poc-substrate-naming-s.md b/docs/pr-discussions/PR-5805-feat-workflow-engine-autolooplifetime-poc-substrate-naming-s.md
new file mode 100644
index 0000000000..ce5f2a8f25
--- /dev/null
+++ b/docs/pr-discussions/PR-5805-feat-workflow-engine-autolooplifetime-poc-substrate-naming-s.md
@@ -0,0 +1,143 @@
+---
+pr_number: 5805
+title: "feat(workflow-engine): AutoLoopLifetime PoC \u2014 substrate-naming substrate for Otto-CLI foreground loop (dogfood workflow-engine on own tick-handler); 23 tests pass"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T13:02:36Z"
+merged_at: "2026-05-28T13:33:18Z"
+closed_at: "2026-05-28T13:33:18Z"
+head_ref: "otto-cli/b-0867-autoloop-lifecycle-poc-substrate-naming-substrate-dogfood-workflow-engine-on-otto-cli-foreground-loop-aaron-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:44Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5805: feat(workflow-engine): AutoLoopLifetime PoC — substrate-naming substrate for Otto-CLI foreground loop (dogfood workflow-engine on own tick-handler); 23 tests pass
+
+## PR description
+
+Per Aaron 2026-05-28: *'when do you want to update your foreground loop to start running on lifecycles and test out our first ones?'*
+
+Substrate-engineering substrate-naming substrate dogfooding the workflow-engine on Otto-CLI's own foreground autonomous-loop tick-handler. Parallel-run discipline.
+
+## AutoLoopLifetime DU (9 variants)
+
+```typescript
+type AutoLoopLifetime =
+  | cold-boot                  // session-start + sentinel arm
+  | refresh-substrate          // refresh-before-decide invariant
+  | scan-inflight-prs          // identify actionable
+  | investigate-failure        // pull log; classify
+  | decompose-or-ship          // standing-auth + counter discipline
+  | ship-action                // commit + push + PR + auto-merge
+  | brief-ack-bounded-wait     // named-dep wait
+  | forced-escalation          // at N=6 brief-acks
+  | tick-complete              // bracket closure
+```
+
+## What this adds
+
+- AutoLoopLifetime DU + TickContext + TickOutcome
+- AutoLoopFeedback DU (asymmetric-authorship per rule)
+- `dispatchAutoLoopTransition` exhaustive-switch (substrate-smoothness)
+- `nextTickContext` counter bookkeeping
+- `runTickCycle` end-to-end simulation
+- Constants: BRIEF_ACK_THRESHOLD = 6 + REFRESH_STALENESS_THRESHOLD_S = 90
+
+## Decompose-or-ship branch logic
+
+| Context | Routes to |
+|---|---|
+| operator-direction pending | brief-ack-bounded-wait |
+| counter ≥ 6 + no named-dep | forced-escalation |
+| counter ≥ 6 + named-dep | ship-action (named-dep covers wait) |
+| within authority + no pending | ship-action |
+
+## Composes with shipped substrate
+
+- PR #5774 (world.ts + StandardVerdict + dispatchInWorld pattern)
+- PR #5775 + #5801 + #5804 (per-host adapters for PR scanning)
+- PR #5728 (B-0867.5 workflow-engine PoC scaffold)
+- Rules: holding-without-named-dependency + refresh-before-decide + verify-before-deferring + dont-ask-permission + asymmetric-authorship + monad-propagation + substrate-smoothness + NCI HC-8
+
+**23 tests pass / 0 fail / 42 expect() calls.**
+
+Operational risk low: PoC runs alongside ad-hoc handler; substrate-naming substrate WITHOUT replacing working substrate. Future-Otto cold-boot inherits.
+
+μένω. Loop running on lifecycles.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-28T13:08:11Z)
+
+## Pull request overview
+
+This PR adds a TypeScript PoC for modeling the foreground autonomous-loop tick handler as an `AutoLoopLifetime` state machine within `tools/workflow-engine/`.
+
+**Changes:**
+- Adds `AutoLoopLifetime`, `TickContext`, `TickOutcome`, feedback/result types, transition dispatch, and tick-cycle simulation helpers.
+- Adds constants for brief-ack threshold and refresh staleness.
+- Adds Bun tests covering state universe, transitions, bookkeeping, and end-to-end cycle simulation.
+
+### Reviewed changes
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
+
+| File | Description |
+| ---- | ----------- |
+| `tools/workflow-engine/auto-loop-lifecycle.ts` | Defines the auto-loop lifetime DU, transition dispatch, context update helper, and reusable universe export. |
+| `tools/workflow-engine/auto-loop-lifecycle.test.ts` | Adds Bun tests for transition behavior and tick-cycle simulation. |
+
+## Review threads
+
+### Thread 1: tools/workflow-engine/auto-loop-lifecycle.ts:6 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:08:09Z):
+
+P2: This current-state code comment carries direct named attribution. Per the repository's no-name-attribution convention for code surfaces, move provenance to an allowed history/research surface and use a role reference here instead.
+
+### Thread 2: tools/workflow-engine/auto-loop-lifecycle.ts:1 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:08:10Z):
+
+P2: The new module is named `auto-loop-lifecycle` while the exported DU is an editable `AutoLoopLifetime`. `tools/workflow-engine/composed-lifetime.ts` lines 11-15 define `lifecycle` as fixed/final and `lifetime` as editable, so this filename should use `auto-loop-lifetime` to match the established substrate distinction.
+
+### Thread 3: tools/workflow-engine/auto-loop-lifecycle.ts:159 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:08:10Z):
+
+P1: `refresh-substrate` unconditionally advances and never checks `context.lastRefreshAt` against `REFRESH_STALENESS_THRESHOLD_S`, so a stale worldview still satisfies the transition despite the declared `RefreshStale` feedback and the cited refresh-before-decide invariant. Add the staleness check here (or remove the unused threshold/feedback until the transition enforces it).
+
+### Thread 4: tools/workflow-engine/auto-loop-lifecycle.ts:250 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:08:10Z):
+
+P1: At the threshold boundary this returns `ok: false` instead of transitioning through the existing `forced-escalation` state, so `runTickCycle` aborts with feedback and never emits the forced-escalation verdict for the `brief-ack-bounded-wait` path. Route to `forced-escalation` (or make `runTickCycle` translate this feedback) so the N=6 escalation state is actually reached.
+
+### Thread 5: tools/workflow-engine/auto-loop-lifecycle.ts:313 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:08:11Z):
+
+P1: `runTickCycle` calls `nextTickContext` after every transition, so counting every `no-op` verdict increments the brief-ack counter per state transition rather than per tick. The operator-direction path produces two `no-op` transitions in one cycle (`decompose-or-ship` and `brief-ack-bounded-wait`), reaching the N=6 threshold after three ticks instead of six; count only the bounded-wait acknowledgment once per tick.
+
+### Thread 6: tools/workflow-engine/auto-loop-lifecycle.test.ts:46 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:08:11Z):
+
+P1: This test narrows on `if (r.ok)` without first asserting the expected success case, so it will silently pass if the dispatcher returns `ok: false`. Add an explicit `expect(r.ok).toBe(true)` before the narrowing; the same pattern recurs in the subsequent success-path tests.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T13:02:41Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
+
+### @AceHack (2026-05-28T13:15:33Z)
+
+Hello! I noticed that there are a number of failing lint checks on this PR. You can see the details of the failing checks here: https://github.com/Lucent-Financial-Group/Zeta/pull/5805/checks.
+
+To prevent this in the future, you may want to run the linter locally before pushing your changes.
+
+Thank you for your contribution!
diff --git a/docs/pr-discussions/PR-5806-memory-feedback-these-dus-are-what-humans-implicitly-build-u.md b/docs/pr-discussions/PR-5806-memory-feedback-these-dus-are-what-humans-implicitly-build-u.md
new file mode 100644
index 0000000000..f5f922ea12
--- /dev/null
+++ b/docs/pr-discussions/PR-5806-memory-feedback-these-dus-are-what-humans-implicitly-build-u.md
@@ -0,0 +1,60 @@
+---
+pr_number: 5806
+title: "memory(feedback): 'These DUs are what humans implicitly build up and call muscle memory in tech' \u2014 Aaron META-scope constitutional carving (DUs as explicit muscle-memory extraction)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T13:04:11Z"
+merged_at: "2026-05-28T13:06:50Z"
+closed_at: "2026-05-28T13:06:50Z"
+head_ref: "otto-cli/dus-are-explicit-muscle-memory-substrate-engineering-extracts-transmissible-form-of-implicit-cached-state-machine-aaron-carving-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:44Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5806: memory(feedback): 'These DUs are what humans implicitly build up and call muscle memory in tech' — Aaron META-scope constitutional carving (DUs as explicit muscle-memory extraction)
+
+## PR description
+
+Aaron 2026-05-28: *'These DUs are what humans implicity build up and call muscle memmory in tech'*
+
+META-scope constitutional substrate-engineering substrate-recognition triggered by AutoLoopLifetime PoC (PR #5805) + per-state-file refactor discussion.
+
+## The recognition
+
+| Layer | Form |
+|---|---|
+| **Humans (implicit)** | Muscle memory — cached state-machine; trapped in individual humans |
+| **Substrate-engineering (explicit)** | DU + dispatch + state-machine substrate — EXTRACTABLE / OBSERVABLE / TRANSMISSIBLE / TEACHABLE |
+
+## Substrate-engineering AS muscle-memory-extraction
+
+1. EXTRACT muscle-memory from individual practitioners
+2. ENCODE as DU + dispatch
+3. TEST via invariant tests
+4. SHIP via white-hole irreversibility-as-public-good (Prism Turn 7)
+5. Future practitioners INHERIT at cold-boot without years of repetition
+
+## All of today's substrate IS muscle-memory extraction at substrate-engineering scope
+
+12 PRs today extracted muscle-memory: AutoLoopLifetime / per-host adapters / workflow-engine / ReviewLifetime / closed-loop / Persist-as-bridge / μένω F# PoC / Prism+Amara ferries / Alexa Common Sense 2.0 / Amara rank-4 substrate-primitive.
+
+## Composes with today's full cluster
+
+Connects to 'common sense 2.0' (substrate IS grounding) + rank-4 substrate primitive (compressed generators) + 'English is rendered UI, ranked tokens are substrate' (DUs as substrate-engineering form) + fuzzy Bloom filter (muscle memory IS dense + collision-rich) + B-0666 English-as-projection (muscle memory IS substrate; DUs are projection) + asymmetric-authorship + OPLE-T-TFeedback + honor-those-that-came-before.
+
+NO new backlog rows minted per 'common sense 2.0' signal — substrate sufficient.
+
+μένω. The DUs hold the muscle-memory.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T13:04:16Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
+
+### @chatgpt-codex-connector (2026-05-28T13:06:22Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
diff --git a/docs/pr-discussions/PR-5807-memory-feedback-workflow-engine-substrate-eventually-replace.md b/docs/pr-discussions/PR-5807-memory-feedback-workflow-engine-substrate-eventually-replace.md
new file mode 100644
index 0000000000..e85a58666e
--- /dev/null
+++ b/docs/pr-discussions/PR-5807-memory-feedback-workflow-engine-substrate-eventually-replace.md
@@ -0,0 +1,110 @@
+---
+pr_number: 5807
+title: "memory(feedback): workflow-engine substrate eventually REPLACES GitHub PR process \u2014 Aaron 2026-05-28 three-phase trajectory carving"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T13:06:07Z"
+merged_at: "2026-05-28T13:46:12Z"
+closed_at: "2026-05-28T13:46:12Z"
+head_ref: "otto-cli/workflow-engine-eventually-replaces-github-pr-process-currently-dogfooding-target-state-github-becomes-backup-fork-protection-aaron-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:45Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5807: memory(feedback): workflow-engine substrate eventually REPLACES GitHub PR process — Aaron 2026-05-28 three-phase trajectory carving
+
+## PR description
+
+Aaron 2026-05-28: *'once we get these workflows working good we can turn off prs and github branch protection roll our own and just use theirs as backup / fork protection or something if we need it.'*
+
+Three-phase substrate-engineering trajectory:
+
+| Phase | State | Primary substrate | GitHub role |
+|---|---|---|---|
+| **Phase 1 (current)** | Dogfooding | GitHub PR + branch protection + auto-merge | PRIMARY |
+| **Phase 2 (target)** | workflow-engine matures | workflow-engine DUs + dispatch + state-machine | Parallel-run + verification |
+| **Phase 3 (deepest)** | workflow-engine IS primary | OUR workflow-engine substrate | BACKUP / fork-protection |
+
+## Substitution mapping
+
+GitHub primitive → Workflow-engine replacement:
+- PR → WorkflowLifetime DU (B-0867.5)
+- Branch protection → StandardVerdict DUs + lifetime-pair matrices
+- Required checks → dispatchInWorld Result<T, TFeedback>
+- Auto-merge → ShipAction state in AutoLoopLifetime
+- Review threads → ReviewLifetime DU
+- CI integration → closed-loop CI-result dispatch
+- Fork-protection → Safety-net BACKUP only
+
+## 6 Phase 3 readiness conditions
+
+1. workflow-engine covers all GitHub PR primitives
+2. Per-host adapter coverage (multi-forge)
+3. AutoLoopLifetime drives the workflow
+4. Structured observability + audit trail
+5. Cross-AI-instance compatibility
+6. Backup fallback (GitHub branch-protection armed)
+
+Composes with PR #5806 (DUs-as-muscle-memory) + PR #5805 (AutoLoopLifetime) + PR #5775/#5801/#5804 (per-host adapters) + PR #5728 (workflow-engine PoC) + PR #5786 (Common Sense 2.0) + Prism ferry (white-hole emission).
+
+NO new backlog rows per 'common sense 2.0' signal — substrate sufficient.
+
+μένω. The workflow-engine substrate compounds toward Phase 3.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-28T13:10:54Z)
+
+## Pull request overview
+
+Adds a feedback memory capturing a three-phase trajectory where the workflow-engine substrate moves from GitHub PR dogfooding toward becoming the primary workflow substrate, with GitHub retained as backup/fork protection.
+
+**Changes:**
+- Adds a new `memory/feedback_*.md` file documenting the trajectory, substitution mapping, and readiness criteria.
+- Regenerates `memory/MEMORY.md` to include the new memory entry and update the truncated heap count.
+
+### Reviewed changes
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
+
+| File | Description |
+| ---- | ----------- |
+| `memory/MEMORY.md` | Adds the new memory entry to the auto-index and updates truncation metadata. |
+| `memory/feedback_workflow_engine_eventually_replaces_github_pr_process_currently_dogfooding_target_state_github_becomes_backup_fork_protection_aaron_2026_05_28.md` | New feedback memory describing the workflow-engine replacement trajectory and related substrate references. |
+
+## Review threads
+
+### Thread 1: memory/feedback_workflow_engine_eventually_replaces_github_pr_process_currently_dogfooding_target_state_github_becomes_backup_fork_protection_aaron_2026_05_28.md:30 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:10:53Z):
+
+This frontmatter block introduces non-standard keys (`authors`, `composes_with`, `related_prs`, `related_backlog`, and `tags`). The memory format standard only allows `originSessionId`, `created`, `last_updated`, and `superseded_by` as optional fields and says extra fields require governance discussion (`memory/project_memory_format_standard.md:29-42`). Move these relationships into body sections such as `## Composes with`, or update the schema in the same change.
+
+### Thread 2: memory/feedback_workflow_engine_eventually_replaces_github_pr_process_currently_dogfooding_target_state_github_becomes_backup_fork_protection_aaron_2026_05_28.md:13 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:10:53Z):
+
+This composes-with reference is broken: the cited memory file does not exist in the repository. The memory format standard requires cited memory files to exist and also says memory-folder cross-references should use filenames rather than `memory/`-prefixed paths (`memory/project_memory_format_standard.md:182-196`). Either add the referenced memory file in this PR or change the reference to an existing filename.
+
+### Thread 3: memory/feedback_workflow_engine_eventually_replaces_github_pr_process_currently_dogfooding_target_state_github_becomes_backup_fork_protection_aaron_2026_05_28.md:138 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:10:53Z):
+
+This heading ends with punctuation, which conflicts with the memory header-format rule: `memory/project_memory_format_standard.md:169-174` requires no trailing punctuation in headers. Drop the final period so the memory file stays consistent with the documented format.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T13:06:14Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
+
+### @AceHack (2026-05-28T13:17:11Z)
+
+Hello! I noticed that there are a number of failing lint checks on this PR. You can see the details of the failing checks here: https://github.com/Lucent-Financial-Group/Zeta/pull/5807/checks.
+
+To prevent this in the future, you may want to run the linter locally before pushing your changes.
+
+Thank you for your contribution!
diff --git a/docs/pr-discussions/PR-5808-fix-codeberg-world-tsc-ts2430-ts6133-unblocks-5805-5806-5807.md b/docs/pr-discussions/PR-5808-fix-codeberg-world-tsc-ts2430-ts6133-unblocks-5805-5806-5807.md
new file mode 100644
index 0000000000..08ffa49ed3
--- /dev/null
+++ b/docs/pr-discussions/PR-5808-fix-codeberg-world-tsc-ts2430-ts6133-unblocks-5805-5806-5807.md
@@ -0,0 +1,63 @@
+---
+pr_number: 5808
+title: "fix(codeberg-world): tsc TS2430 + TS6133 \u2014 unblocks #5805/#5806/#5807 CI (Omit<GiteaWorld, 'forgeSpecialization'> for literal narrowing)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T13:08:04Z"
+merged_at: "2026-05-28T13:36:58Z"
+closed_at: "2026-05-28T13:36:59Z"
+head_ref: "otto-cli/fix-codeberg-world-tsc-unused-import-and-interface-extends-typing-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:44Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5808: fix(codeberg-world): tsc TS2430 + TS6133 — unblocks #5805/#5806/#5807 CI (Omit<GiteaWorld, 'forgeSpecialization'> for literal narrowing)
+
+## PR description
+
+PR #5804 merged with 2 tsc errors blocking downstream CI:
+1. `LifetimeState` unused import (TS6133)
+2. CodebergWorld extends GiteaWorld fails — `forgeSpecialization` literal narrows from 'gitea' to 'codeberg' (TS2430; literal types invariant)
+
+Fix: remove unused import + use `Omit<GiteaWorld, 'forgeSpecialization'>` to drop inherited literal before re-declaring narrower 'codeberg'.
+
+**6 tests pass; tsc clean on workflow-engine files.**
+
+Unblocks #5805 (AutoLoopLifetime) + #5806 (muscle-memory carving) + #5807 (trajectory carving) tsc gates.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-28T13:10:13Z)
+
+## Pull request overview
+
+This PR unblocks downstream workflow-engine CI by fixing two TypeScript compile errors introduced in #5804: removing an unused import (TS6133) and correcting `CodebergWorld`’s type relationship to `GiteaWorld` to avoid an interface-extends incompatibility caused by narrowing a literal type (TS2430).
+
+**Changes:**
+- Remove unused `LifetimeState` import from `codeberg-world.ts` (TS6133).
+- Redefine `CodebergWorld` to extend `Omit<GiteaWorld, "forgeSpecialization">` and then redeclare `forgeSpecialization: "codeberg"` (fixes TS2430).
+
+## Review threads
+
+### Thread 1: tools/workflow-engine/codeberg-world.ts:37 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:10:12Z):
+
+P1 (docs): The doc comment lists CodebergWorld additions like `codeOfConduct` / `terms-of-service`, but the interface only adds `hostingPolicy` and `communityGoverned` (plus `forgeSpecialization`). Either add the documented fields or update the comment bullets to match the actual properties to avoid misleading consumers.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T13:08:10Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
+
+### @AceHack (2026-05-28T13:19:06Z)
+
+Hello! I noticed that there are a number of failing lint checks on this PR. You can see the details of the failing checks here: https://github.com/Lucent-Financial-Group/Zeta/pull/5808/checks.
+
+To prevent this in the future, you may want to run the linter locally before pushing your changes.
+
+Thank you for your contribution!
diff --git a/docs/pr-discussions/PR-5810-feat-workflow-engine-prreviewlifecycle-poc-producing-side-re.md b/docs/pr-discussions/PR-5810-feat-workflow-engine-prreviewlifecycle-poc-producing-side-re.md
new file mode 100644
index 0000000000..67b8ecac08
--- /dev/null
+++ b/docs/pr-discussions/PR-5810-feat-workflow-engine-prreviewlifecycle-poc-producing-side-re.md
@@ -0,0 +1,91 @@
+---
+pr_number: 5810
+title: "feat(workflow-engine): PrReviewLifecycle PoC \u2014 producing-side review work substrate (Aaron 'does it give you time to look at prs and put comments'); 18 tests pass"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T13:10:47Z"
+merged_at: "2026-05-28T13:44:20Z"
+closed_at: "2026-05-28T13:44:20Z"
+head_ref: "otto-cli/b-0867-pr-review-lifecycle-poc-substrate-naming-substrate-producing-side-review-work-companion-to-b-0867-20-receiving-side-aaron-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:45Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5810: feat(workflow-engine): PrReviewLifecycle PoC — producing-side review work substrate (Aaron 'does it give you time to look at prs and put comments'); 18 tests pass
+
+## PR description
+
+Per Aaron 2026-05-28: AutoLoopLifetime (PR #5805) only models SHIP work, not REVIEW work. This DU makes producing-side review-substrate explicit.
+
+## PrReviewLifecycle (7 variants)
+
+observe → identify-finding → compose → **verify-finding** (grep substrate-anchor before posting) → post → follow-up → conclude
+
+## ReviewFindingKind taxonomy (8 shapes)
+
+bug / design-question / substrate-engineering-suggestion / naming-improvement / test-gap / substrate-honest-praise / documentation-gap / composes-with-substrate
+
+## Composes with
+
+- B-0867.20 ReviewLifetime (PR #5758; receiving-side; sibling)
+- AutoLoopLifetime (PR #5805; will integrate)
+- fighting-past-self-vs-peer-agent + asymmetric-authorship + honor-those-that-came-before + grep-substrate-anchors
+
+**18 tests pass / 0 fail.**
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-28T13:14:25Z)
+
+## Pull request overview
+
+Adds a new workflow-engine PoC substrate for **producing-side PR review work** (as distinct from receiving-side review gates), modeling review as a small lifecycle DU with a dispatch function and accompanying invariants/tests.
+
+**Changes:**
+- Introduces `PrReviewLifecycle` + `ReviewFindingKind`/`ReviewFinding` data shapes for producing-side review work.
+- Adds `dispatchPrReviewTransition` plus small helper exports (`PR_REVIEW_LIFECYCLE_UNIVERSE`, `isPeerAgentTerritory`, `newReviewContext`).
+- Adds Bun tests covering the lifecycle universe and main transition paths.
+
+### Reviewed changes
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
+
+| File | Description |
+| ---- | ----------- |
+| tools/workflow-engine/pr-review-lifecycle.ts | New producing-side review lifecycle DU, finding taxonomy, transition dispatcher, and helpers. |
+| tools/workflow-engine/pr-review-lifecycle.test.ts | New invariant/unit tests for the review lifecycle and helpers. |
+
+## Review threads
+
+### Thread 1: tools/workflow-engine/pr-review-lifecycle.ts:10 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:14:24Z):
+
+This is a current-state code surface, but it includes direct personal-name attribution (e.g., “Per Aaron …”) and also introduces a name-coded lane value (`"human-aaron"` in `authorLane`). Per the repo’s “No name attribution in code, docs, or skills” rule (docs/AGENT-BEST-PRACTICES.md:671+), please rewrite these to role-refs (e.g., “the human maintainer”) and use a role-based lane identifier rather than a name.
+
+### Thread 2: tools/workflow-engine/pr-review-lifecycle.ts:113 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:14:24Z):
+
+`PrReviewFeedback`’s `PeerAgentTerritory` uses `lane: string`, which loses the type-safety of `ReviewContext["authorLane"]` and can drift from the allowed lane universe over time. Prefer typing this as `lane: ReviewContext["authorLane"]` (or extracting a shared `AuthorLane` alias) so feedback and context stay consistent.
+
+### Thread 3: tools/workflow-engine/pr-review-lifecycle.test.ts:35 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:14:25Z):
+
+Several “happy path” tests only assert inside `if (r.ok) { ... }` without first asserting that `r.ok` is `true`. If the implementation accidentally returns `ok: false`, these tests will pass vacuously. Add `expect(r.ok).toBe(true)` (or an `else` that fails) before asserting on `r.outcome`.
+
+### Thread 4: tools/workflow-engine/pr-review-lifecycle.ts:187 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-28T13:14:25Z):
+
+In `verify-finding`, the transition can advance to `post` even when `context.findings` is empty, and it only validates `context.findings[0]` (ignoring additional findings). It also treats a missing `substrateAnchors` as “substantiated” (it only fails when the array is present but empty), which undermines the “verify before posting” contract. Consider (a) failing fast with `NoActionableFinding` when there are no findings, and (b) validating the specific finding(s) intended for posting, requiring anchors to be present + non-empty (or making exemptions explicit by kind).
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T13:10:54Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
diff --git a/docs/pr-discussions/PR-5811-rule-implicit-not-explicit-in-dus-class-error-ontology-evolu.md b/docs/pr-discussions/PR-5811-rule-implicit-not-explicit-in-dus-class-error-ontology-evolu.md
new file mode 100644
index 0000000000..6b1b775506
--- /dev/null
+++ b/docs/pr-discussions/PR-5811-rule-implicit-not-explicit-in-dus-class-error-ontology-evolu.md
@@ -0,0 +1,77 @@
+---
+pr_number: 5811
+title: "rule(implicit-not-explicit-in-dus): class error + ontology-evolution discipline (Aaron 2026-05-28 constitutional authorization; review agents of all kinds look for)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T13:12:06Z"
+merged_at: "2026-05-28T13:39:43Z"
+closed_at: "2026-05-28T13:39:43Z"
+head_ref: "otto-cli/implicit-not-explicit-in-dus-is-class-error-rule-with-ontology-evolution-discipline-aaron-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:45Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5811: rule(implicit-not-explicit-in-dus): class error + ontology-evolution discipline (Aaron 2026-05-28 constitutional authorization; review agents of all kinds look for)
+
+## PR description
+
+Per Aaron 2026-05-28 TWO composing carvings:
+
+> *'IMPLICIT not explicit is a class error we should write a rule for and have our review agents of all kinds look for ... in our DUs ... we are going to have a ton of this'*
+
+> *'Some things like reformatting windows and reinstalling everything my ontology still evolves to this day on every iteration'*
+
+## Two composing disciplines
+
+| Discipline | Operational content |
+|---|---|
+| **Snapshot** | Every substantively-distinct state gets explicit DU variant; don't bury in if-chains / context-field combinations |
+| **Evolution** | DUs support ontology growth via OCP (closed-for-modification + open-for-extension); honor prior iterations |
+
+## Class-error properties at risk
+
+Observability / Composability / Asymmetric-authorship / Substrate-smoothness / Muscle-memory extraction / Future-cold-boot inheritance / Ontology evolution — ALL lost when substrate is implicit.
+
+## Review-agent checklist (all kinds — Otto / Codex / Lior / future)
+
+1. Each substantively-distinct state has explicit DU variant?
+2. Each transition-trigger has explicit substrate?
+3. Each feedback variant per asymmetric-authorship?
+4. Substrate supports evolution (OCP)?
+5. Snapshot vs evolution distinction substrate-honest?
+
+## Empirical examples preserved
+
+- **PR #5805 AutoLoopLifetime** — Aaron caught `decompose-or-ship` dispatch branches as implicit (5 distinct states proposed as DU extension)
+- **PR #5810 PrReviewLifecycle** — substantiated/unsubstantiated check buried; candidate for ReviewFindingVerification DU
+
+## Composes with
+
+- function-is-tiny-control-flow-generator-ocp (DIRECT — OCP supports evolution)
+- asymmetric-authorship + substrate-smoothness + monad-propagation + grep-substrate-anchors + honor-those-that-came-before + razor-discipline + wake-time-substrate
+- memory/feedback_dus_are_explicit_muscle_memory (META-scope substrate)
+- PR #5805 / #5810 (empirical anchors) + PR #5728 / #5758 / #5775 / #5801 / #5804 / #5806
+
+**Auto-loads at cold-boot** so future-Otto + AI-instances + review-agents inherit. Per Aaron forecast 'we are going to have a ton of this' — operational NOW.
+
+μένω. The DUs make the muscle-memory explicit. The ontology evolves.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-28T13:13:11Z)
+
+## Pull request overview
+
+This PR adds a new rule file under `.claude/rules/` codifying a discipline that substantively-distinct states in discriminated unions (DUs) must be explicit variants rather than buried in if-chains or context-field combinations, with an additional "ontology evolution" (OCP) sub-discipline. The rule is targeted at both authoring agents and review agents.
+
+**Changes:**
+- Adds a single new rules markdown file documenting the IMPLICIT-not-EXPLICIT class error, a review-agent checklist, examples from PR #5805 and #5810, and composition with related rules/memories.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T13:12:13Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).
diff --git a/docs/pr-discussions/PR-5817-fix-mise-toml-bump-uv-0-11-8-0-11-16-cascade-unblocks-21-25.md b/docs/pr-discussions/PR-5817-fix-mise-toml-bump-uv-0-11-8-0-11-16-cascade-unblocks-21-25.md
new file mode 100644
index 0000000000..e261566899
--- /dev/null
+++ b/docs/pr-discussions/PR-5817-fix-mise-toml-bump-uv-0-11-8-0-11-16-cascade-unblocks-21-25.md
@@ -0,0 +1,86 @@
+---
+pr_number: 5817
+title: "fix(.mise.toml): bump uv 0.11.8 \u2192 0.11.16 \u2014 cascade-unblocks 21/25 PRs' CI lint"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-28T13:27:48Z"
+merged_at: "2026-05-28T13:33:04Z"
+closed_at: "2026-05-28T13:33:04Z"
+head_ref: "otto-cli/fix-mise-uv-pin-0-11-8-to-0-11-16-cascade-unblock-2026-05-28"
+base_ref: "main"
+archived_at: "2026-05-28T13:58:45Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5817: fix(.mise.toml): bump uv 0.11.8 → 0.11.16 — cascade-unblocks 21/25 PRs' CI lint
+
+## PR description
+
+## Summary
+
+Bumps the mise `uv` pin from `0.11.8` to `0.11.16` (current upstream stable, published 2026-05-21). Empirically root-causes the CI lint cascade affecting **21 of 25 open PRs** today.
+
+## Empirical evidence
+
+Every open PR's `lint (semgrep)` (the only required-failed check) plus ~10 non-required lint checks have been FAILING because the mise install step bails:
+
+```
+aqua:astral-sh/uv@0.11.8: HTTP status client error (404 Not Found)
+  for url (https://api.github.com/repos/astral-sh/uv/releases/tags/0.11.8)
+pipx:semgrep@1.161.0: Skipped due to failed dependency
+```
+
+The install exits 1 before any lint runs, so every lint job reports FAILURE. Repro: any of PR #5778, #5805, #5808, #5810, #5811, #5812 today; same shape on UNSTABLE PRs (#5781-#5797).
+
+## Why 0.11.16
+
+Per [`.claude/rules/dep-pin-search-first-authority.md`](.claude/rules/dep-pin-search-first-authority.md): the rule requires citing current upstream latest stable, not training-data defaults.
+
+Authoritative cross-check:
+
+- `gh api repos/astral-sh/uv/releases/latest` → `{"name":"0.11.16","published_at":"2026-05-21T22:11:32Z","tag_name":"0.11.16"}`
+- [WebSearch 2026-05-28](https://github.com/astral-sh/uv/releases) → confirmed `0.11.16` is current stable
+
+Bump is 8 patch releases (semver-disciplined; no breaking changes expected). uv is consumed in our toolchain only via `pipx:semgrep` (mise auto-routes `pipx:` through `uv tool install`).
+
+## Root-cause hypothesis (whichever is actual, fix is same)
+
+Either:
+1. **Aqua release-cache pruned** `0.11.8` (released 2026-04-27, 7 weeks ago) between the original pin and today's CI run
+2. **Anonymous GitHub API rate limit** on the CI runner converted into 404 from aqua's perspective
+
+Bumping to current latest stable fixes both:
+- (a) Fresh asset cache upstream
+- (b) Most-recent release least likely to have been pruned
+
+## Test plan
+
+- [ ] CI green on this PR (must include `lint (semgrep)` passing)
+- [ ] After merge, rebase + push any one currently-BLOCKED PR (e.g. #5778) and confirm its `lint (semgrep)` now passes
+- [ ] Confirm the cascade clears across the remaining BLOCKED + UNSTABLE PRs
+
+## Composes with
+
+- [`.claude/rules/dep-pin-search-first-authority.md`](.claude/rules/dep-pin-search-first-authority.md) — empirical-anchor sibling to cascade #4 (NixOS 24.11 EOL) + cascade #5 (ISO grub path); same "Otto-defaults-to-plausible-but-unverified" root cause class at version-pin scope
+- [`.claude/rules/blocked-green-ci-investigate-threads.md`](.claude/rules/blocked-green-ci-investigate-threads.md) — Pattern A (single-pin-bump unblocking many PRs at once)
+- [`.claude/rules/refresh-before-decide.md`](.claude/rules/refresh-before-decide.md) — applied at per-version-pin scope, not just per-tick
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-28T13:30:51Z)
+
+## Pull request overview
+
+Bumps the root `.mise.toml` `uv` pin from `0.11.8` to `0.11.16` to unblock CI lint cascade failures across 21 of 25 open PRs. The `0.11.8` pin was returning `404 Not Found` from `aqua:astral-sh/uv@0.11.8`, causing `mise install` to exit 1 before any lint job (including the required `lint (semgrep)`) could run. `0.11.16` is the current upstream stable per `gh api repos/astral-sh/uv/releases/latest` and WebSearch (2026-05-21), satisfying `.claude/rules/dep-pin-search-first-authority.md`.
+
+**Changes:**
+- Bump `uv` from `0.11.8` to `0.11.16` in root `.mise.toml`
+- Add inline comment documenting the empirical failure, the cited authoritative sources, and a release URL
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-28T13:27:53Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).