docs(archive): Batch archive of 20 PRs

docs/pr-discussions/PR-5511-docs-rule-land-monad-propagation-pattern-cross-language-subs.md

@@ -0,0 +1,93 @@
+---
+pr_number: 5511
+title: "docs(rule): land monad-propagation-pattern-cross-language-substrate-shape rule (Aaron 2026-05-27)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T16:49:54Z"
+merged_at: "2026-05-27T16:59:39Z"
+closed_at: "2026-05-27T16:59:39Z"
+head_ref: "backlog/monad-propagation-pattern-cross-language-substrate-shape-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T19:20:49Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5511: docs(rule): land monad-propagation-pattern-cross-language-substrate-shape rule (Aaron 2026-05-27)
+
+## PR description
+
+## Summary
+
+Operator-directed substrate-landing of the monad-propagation pattern
+identified through the 2026-05-27 substrate-engineering thread that
+produced PR #5505 + #5507:
+
+> *\"we should save that modan propatation pattern we can generate
+> code from specs easlier in the future if we build around these
+> patterns our code becomes more similar shapped across languages.
+> and we have some amount of composiblity in what's ususaly not
+> composable like recursive CTE composiblity.\"*
+
+## Three-component pattern
+
+1. **Discriminator-carrier** — existing primitive (sum-type / NULL /
+   sentinel / enum)
+2. **Lazy-propagation via composition primitive** — Result.bind /
+   recursive CTE UNION ALL / ? operator / Promise.then / monadic do
+3. **Consumer must handle exhaustively or propagate** — compile-time
+   match-warning / lint discipline / CHECK constraint / sealed-type /
+   explicit early-return
+
+## What the rule adds
+
+- 10-row cross-language instantiation table (F# / Rust / TypeScript /
+  T-SQL / Postgres / C# / Java / C++ / Go / Python)
+- 3-section operational benefits analysis: spec-to-code generation +
+  cross-language similarity + composability-where-usually-missing
+- SQL recursive CTE composability example via feedback_type column
+  flowing through CTE chains
+- Composition with 6 substrate elements + 8 framework rules
+- 6-step authoring discipline + 3-step review discipline
+- Substrate-honest framing
+
+## Test plan
+
+- [x] Markdownlint clean (no MD004 leading-+ continuations)
+- [x] No MD024 duplicate-heading issues
+- [x] All backtick paths on single lines
+- [ ] CI passes (auto-merge to fire on green)
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T16:55:14Z)
+
+## Pull request overview
+
+This PR adds an always-on Claude rule documenting a cross-language “monad-propagation” substrate pattern for uniform feedback/error propagation across languages and SQL recursive CTEs.
+
+**Changes:**
+- Adds a new `.claude/rules/` rule defining the three-part pattern.
+- Provides cross-language instantiation examples and operational benefits.
+- Connects the rule to related framework rules and substrate concepts.
+
+## Review threads
+
+### Thread 1: .claude/rules/monad-propagation-pattern-cross-language-substrate-shape.md:7 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:55:13Z):
+
+This wrapped blockquote line starts with `+`, which Markdown treats as a list marker rather than prose. Reword it (for example, use “and consumer…” or move the plus to the previous line) so the carved sentence renders as one sentence and follows the repo’s no-leading-`+` continuation convention.
+
+### Thread 2: .claude/rules/monad-propagation-pattern-cross-language-substrate-shape.md:155 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:55:14Z):
+
+This claims the new substrate was identified through grep, but the rule body does not include the required inline substrate-inventory audit trail from `verify-existing-substrate-before-authoring.md` (what was searched, top hits, and conclusion). Add that audit trail and include the existing SQL NULL/Maybe recursive-CTE substrate hits such as B-0824 and `docs/research/zeta-sql-null-maybe-recursive-cte-generate-join.md`, which cover the same monad/recursive-CTE pattern.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T16:50:01Z)
+
+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).

docs/pr-discussions/PR-5512-docs-b-0861-make-conversation-interface-result-t-convfeedbac.md

@@ -0,0 +1,124 @@
+---
+pr_number: 5512
+title: "docs(B-0861): Make conversation-interface Result<T, ConvFeedback> first-class \u2014 NCI enforcement at operator-Otto conversation scope (Aaron 2026-05-27)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T16:55:33Z"
+merged_at: "2026-05-27T17:03:38Z"
+closed_at: "2026-05-27T17:03:38Z"
+head_ref: "backlog/b-0861-convfeedback-first-class-conversation-interface-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T19:20:48Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5512: docs(B-0861): Make conversation-interface Result<T, ConvFeedback> first-class — NCI enforcement at operator-Otto conversation scope (Aaron 2026-05-27)
+
+## PR description
+
+## Summary
+
+Operator-directed substrate-engineering target row:
+
+> *\"yeah we should make it first class that's a great idea otto\"*
+
+Following PR #5511 monad-propagation-pattern-cross-language-substrate-
+shape rule with NCI-at-conversation-interface section sketching
+Result<T, ConvFeedback> for operator-Otto interaction.
+
+4-component substrate-engineering proposal:
+
+1. ConvFeedback variant taxonomy formalization (starting from 11-
+   variant candidate taxonomy)
+2. Otto-side emission discipline
+3. Operator-side acknowledgment substrate
+4. 6 substrate-engineering target sub-rows for incremental
+   implementation
+
+10-row composition table mapping existing framework rules to ConvFeedback
+variants making implicit signals explicit.
+
+Priority: P2 (substrate-engineering target; future work).
+
+## Test plan
+
+- [x] Markdownlint clean (no MD004 leading-+ continuations)
+- [x] No prior B-0861 row + no in-flight (ID-allocation discipline)
+- [x] Substrate-verification pass per rule
+- [ ] CI passes (auto-merge to fire on green)
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T16:58:24Z)
+
+## Pull request overview
+
+Adds a new P2 backlog row (B-0861) proposing a “conversation-interface as `Result<T, ConvFeedback>`” substrate shape to make NCI-relevant signals explicit and mechanically acknowledgeable in operator–Otto interaction.
+
+**Changes:**
+- Introduces backlog row B-0861 with a proposed ConvFeedback variant taxonomy, emission discipline, and operator acknowledgment scheme.
+- Defines an implementation decomposition into 6 future sub-rows and a rule-to-variant composition table.
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T17:02:38Z)
+
+## Pull request overview
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
+
+## Review threads
+
+### Thread 1: docs/backlog/P2/B-0861-make-conversation-interface-result-t-convfeedback-first-class-operator-otto-nci-enforcement-aaron-2026-05-27.md:33 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:58:22Z):
+
+The text says "Three substrate-engineering components" but the document defines 4 components (Component 1–4). Update the count or renumber so the framing matches the structure.
+
+### Thread 2: docs/backlog/P2/B-0861-make-conversation-interface-result-t-convfeedback-first-class-operator-otto-nci-enforcement-aaron-2026-05-27.md:114 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:58:23Z):
+
+This markdown table is written with double leading pipes (`|| ...`) which renders an extra empty column in GitHub-flavored markdown. Use a standard table form with single leading/trailing pipes so the table renders as intended.
+
+### Thread 3: docs/backlog/P2/B-0861-make-conversation-interface-result-t-convfeedback-first-class-operator-otto-nci-enforcement-aaron-2026-05-27.md:50 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:58:23Z):
+
+In the variant sketch, `Ok of substantive-content` uses a hyphenated identifier (`substantive-content`) which isn’t a valid identifier in TypeScript/F# without special quoting. If these names are meant to transfer directly into a DU/union type, use an identifier-safe form (e.g., `substantiveContent` / `substantive_content`).
+
+### Thread 4: docs/backlog/P2/B-0861-make-conversation-interface-result-t-convfeedback-first-class-operator-otto-nci-enforcement-aaron-2026-05-27.md:132 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:58:23Z):
+
+This row references `.claude/rules/monad-propagation-pattern-cross-language-substrate-shape.md`, but that file does not exist in the current tree. If the intent is “this file will land in PR #5511”, consider changing this to a PR link/reference (or explicitly marking the path as provisional) to avoid a broken cross-reference if #5511 changes or doesn’t merge first.
+
+### Thread 5: docs/backlog/P2/B-0861-make-conversation-interface-result-t-convfeedback-first-class-operator-otto-nci-enforcement-aaron-2026-05-27.md:7 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:58:23Z):
+
+Frontmatter `ask:` uses lowercase `aaron`. Other backlog rows typically capitalize names (e.g., `ask: Aaron 2026-...`). Consider capitalizing for consistency/searchability.
+
+### Thread 6: docs/backlog/P2/B-0861-make-conversation-interface-result-t-convfeedback-first-class-operator-otto-nci-enforcement-aaron-2026-05-27.md:116 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T17:02:37Z):
+
+The markdown table header/rows start with `||`, which introduces an unintended empty first column and renders inconsistently. Use a standard table form with a single leading/trailing `|` per row (e.g., `| Existing rule | … |`).
+
+### Thread 7: docs/backlog/P2/B-0861-make-conversation-interface-result-t-convfeedback-first-class-operator-otto-nci-enforcement-aaron-2026-05-27.md:133 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T17:02:38Z):
+
+This row references `.claude/rules/monad-propagation-pattern-cross-language-substrate-shape.md`, but that file is not present in the repo (so the path is a dead reference unless another PR lands first). Consider referencing the PR/commit explicitly, or landing the rule file in the same PR (or adjusting the wording to avoid a concrete file-path reference until it exists).
+
+### Thread 8: docs/backlog/P2/B-0861-make-conversation-interface-result-t-convfeedback-first-class-operator-otto-nci-enforcement-aaron-2026-05-27.md:36 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T17:02:38Z):
+
+The text says "Three substrate-engineering components" but the section defines Components 1–4 below. Update the count or adjust the structure so the framing matches the actual components listed.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T16:55:37Z)
+
+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).

docs/pr-discussions/PR-5514-docs-research-add-drift-report-on-agent-paralysis.md

@@ -0,0 +1,73 @@
+---
+pr_number: 5514
+title: "docs(research): Add drift report on agent paralysis"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T17:05:10Z"
+merged_at: "2026-05-27T17:18:08Z"
+closed_at: "2026-05-27T17:18:09Z"
+head_ref: "lior/agent-paralysis-drift-report-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T19:20:46Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5514: docs(research): Add drift report on agent paralysis
+
+## PR description
+
+This PR contains a drift report detailing the paralysis of agents Otto, Riven, and Kiro, as well as Lior's self-correction on PR noise. This PR addresses the issues from PR #5496.
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T17:08:05Z)
+
+## Pull request overview
+
+Adds a new research drift report documenting a multi-agent “paralysis” incident in the Zeta factory (Otto/Kiro/Riven) and records recommended mitigations around worktree/clone isolation and PR-noise reduction.
+
+**Changes:**
+- Introduces a structured drift report with executive summary, per-agent findings, and recommendations.
+- Captures concrete operational observations (dirty/contested worktrees, volatile `/tmp` worktree path) and proposed remediation steps.
+
+### COMMENTED — @AceHack (2026-05-27T17:14:28Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-05-27T17:14:38Z)
+
+_(no body)_
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T17:15:45Z)
+
+## Pull request overview
+
+Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
+
+## Review threads
+
+### Thread 1: docs/research/agent-paralysis-drift-report-2026-05-27.md:18 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T17:08:04Z):
+
+P1: The reference to “isolated worktree protocol (B-0751)” is not currently resolvable in-tree (there is no backlog row/document with `id: B-0751`). This makes the citation hard to verify; consider citing the concrete artefact that exists (e.g., PR #5019 per-agent isolated clones) and/or a backlog row that exists (e.g., B-0750 worktree hygiene), and align the wording with what B-0751 is described as elsewhere (“per-agent isolated clones architecture”).
+
+**@AceHack** (2026-05-27T17:14:28Z):
+
+Fixed in 67aa9848f — replaced the B-0751 reference at line 18 with PR #5019 (closed proposal) + B-0750 (worktree-hygiene row in tree) + agent-worktree-hygiene rule path. All three artifacts are resolvable in-tree.
+
+### Thread 2: docs/research/agent-paralysis-drift-report-2026-05-27.md:39 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T17:08:05Z):
+
+P1: “per-agent isolated clone/worktree architecture (B-0751)” appears to cite a backlog row that isn’t present in the repo (`id: B-0751` not found). To keep this recommendation actionable, cite the existing source of truth (PR #5019 and/or the relevant backlog row such as B-0750) or add a linkable reference that exists in-tree.
+
+**@AceHack** (2026-05-27T17:14:38Z):
+
+Fixed in 67aa9848f — replaced the B-0751 reference at line 38 with PR #5019 (closed design proposal) + B-0750 (worktree-hygiene row that exists in tree). Both are linkable + verifiable.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T17:05: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).