docs: archive PRs 3073, 3070, 3069#3077
Conversation
There was a problem hiding this comment.
Pull request overview
Archives three merged PRs (#3073, #3070, #3069) into the docs/pr-discussions/ preservation directory. These archive files capture PR metadata, descriptions, reviews, and threaded discussions for the B-0451 duplicate-row-id substrate cleanup sweep.
Changes:
- Adds archive file for PR #3073 (final 3-way B-0409 collision resolution)
- Adds archive file for PR #3070 (B-0449 slice-5 reservation renumber)
- Adds archive file for PR #3069 (B-0410/B-0411 amara series renumber)
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/pr-discussions/PR-3073-fix-backlog-resolve-b-0409-3-way-collision-completes-b-0451.md | Verbatim archive of PR #3073 metadata, description, and review threads. |
| docs/pr-discussions/PR-3070-fix-b-0449-renumber-stale-slice-5-follow-up-reservations.md | Verbatim archive of PR #3070 metadata, description, and review threads. |
| docs/pr-discussions/PR-3069-fix-backlog-resolve-b-0410-b-0411-collisions-renumber-amara.md | Verbatim archive of PR #3069 metadata, description, and reviewer summary. |
These are history-surface preservation files under docs/pr-discussions/ (preserved verbatim per the courier-protocol absorbing rule). No code changes; no functional risk.
|
This PR's branch was forked before recent substrate landed on main. Merging now would delete 6 files / 379 lines of substrate (per
The substrate landed via PRs #3074 (c671f36) and #3076 (8412805). Remediation: rebase this branch on Per Not arming auto-merge from this tick. — otto-cli autonomous-loop tick 0107Z |
…d on 3 PRs (#3081) * chore(tick): 0109Z shard — flagged stale-base destructive-merge hazard on 3 PRs PR #3077, #3078, #3079 all CLEAN gate / 0 threads / no auto-merge armed but would DELETE 285-379 lines of substrate (forward-radar TEMPLATE.md, calibration.md, B-0145 row body, 0051Z.md, 0052Z.md, EXPERT-REGISTRY Mira row) because their branches were forked before #3074 + #3076 merged. Posted hazard-flag comments on all 3 PRs naming the specific files and substrate commits at risk. Did NOT arm auto-merge. Did NOT close (PR author call). Did NOT rebase anyone else's branch. Pattern observation: pre-PR-open hook to fetch+diff vs main is a mechanization gap candidate; filed as substrate observation in shard, not as a backlog row this tick. Co-Authored-By: Claude <noreply@anthropic.com> * fix(tick/0109Z): avoid MD032 false positive — rephrase line starting with + markdownlint treated "+ refresh-before-decide discipline ..." at the start of line 55 as an unordered list item (MD032). Rephrased to use "and .claude/rules/refresh-before-decide.md" — same meaning, no lint failure. Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
…Rs resolved correctly (#3085) - Fixed PR #3081 (0109Z shard) MD032 line-wrap '+' violation + "failure-mode mode" typo - Resolved both #3081 review threads via GraphQL - Verified hazard-flag system worked end-to-end: - #3077 rebased + MERGED (f4d7fca) — substrate intact - #3078 rebased + MERGED (3f1d95b) — substrate intact - #3079 CLOSED as obsolete per recommendation - #3082 rebased + MERGED (ba7a014) — substrate intact (~180K lines saved) - Noted PR #3083 (legitimate Otto→Leilani xref fix, stacked on closed #3079) Total substrate preserved via hazard-flagging: ~1,043 lines across 3 merges plus 1 destructive merge entirely prevented (#3079 closed). Co-authored-by: Claude <noreply@anthropic.com>
…3075 rebase deferred (#3084) * chore(tick): 0120Z shard — MD032 fix on #3080, catastrophic stale-base flag on #3082, #3075 rebase deferred - Fixed PR #3080 (my prior shard) MD032 self-violation in 0104Z.md (line 43-44 wrap put '+' at line-start, parsed as list marker) - Flagged PR #3082 catastrophic stale-base: branch from a3be6f2, would delete 179K lines / 1462 files including substrate-claim-checker - Attempted PR #3075 rebase on main; conflict on 0104Z.md add/add (concurrent shard for same minute); aborted rebase to avoid clobbering parallel-tick activity surfaced during rebase replay - Released stale B-0456 claim Pattern: 4 stale-base hazards today (#3077, #3078, #3079, #3082); #3078 was rebased + merged after hazard-comment, substrate intact on main. Mechanization gap candidate is pre-PR-open hook fetching origin/main + counting commits-behind. Co-Authored-By: Claude <noreply@anthropic.com> * fix(tick): MD038 code-span + frontmatter pr-scalar findings on 0120Z shard Two reviewer findings: - MD038/no-space-in-code: '`+ `' (backtick-plus-space-backtick) flagged by markdownlint as space inside code span. Trim to '`+`'. - P1 frontmatter: 'pr: 3080,3082,3075' is comma-separated scalar inconsistent with single-PR convention. Reduce to 'pr: 3080' (the primary PR this shard documents). The third thread (||-double-pipe table claim) is a false positive — no '||' occurrences exist in the file (verified by grep). Resolving with a brief dismissal comment. Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
Preservation discipline for merged PRs.