Skip to content

hygiene(#268): pr-preservation drain-log for #219 (Amara 3rd-ferry absorb)#442

Merged
AceHack merged 2 commits intomainfrom
drain/219-pr-preservation-log
Apr 25, 2026
Merged

hygiene(#268): pr-preservation drain-log for #219 (Amara 3rd-ferry absorb)#442
AceHack merged 2 commits intomainfrom
drain/219-pr-preservation-log

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 25, 2026

Summary

Otto-268 backfill: drain-log for PR #219 (aurora absorb of Amara's 3rd courier ferry — decision-proxy + technical review), covering 12 threads.

Per Otto-250 (PR review comments + responses + resolutions are high-quality training signals).

Coverage — three outcome classes

  • FIX (7 threads): typo (adheardceadherence x2 dup), inline-code-span line-wrap reflows (4 threads on memory + nsa-test-history paths), phase-numbering (sixth-phase + 5-phases-total), external-source verifiability (URLs + arXiv:2203.16684 + DOI), CURRENT-amara.md path + annotation.
  • STALE-RESOLVED-BY-REALITY (3 threads): memory file project_lfg_is_demo_facing_*.md now in-tree per Otto-114.
  • OTTO-279 SURFACE-CLASS (2 threads): "Aaron" name in aurora-archive Attribution section + section header — aurora is history-class; first-name attribution preserves provenance, not policy.

Pattern observations

  1. External-source verifiability is a research-doc reproducibility discipline. Adding URLs + arXiv IDs + DOIs is one-line-each but converts "grounded somewhere" into "reviewers can verify."
  2. Inline-code-span line-wrap is the most-recurring formatting bug in this drain wave (4 threads here; same on frontier-readiness: gap #5 audit — 3 directory-level audits (agents + openspec + github) #191 / frontier-readiness: bootstrap reference docs skeleton (gap #4) #195). Pre-commit-lint candidate.
  3. Otto-279 history-surface uniformity matured into a one-paragraph stamp reply for aurora-archive Attribution sections.
  4. Phase-numbering / count-vs-surface-list cardinality findings recur across docs (here: "fifth phase" vs "Phase 6" vs 5-phases-listed; same shape as frontier-readiness: gap #5 audit — 3 directory-level audits (agents + openspec + github) #191 "18 audits" vs 8 actual). Future doc-lint candidate.

Test plan

  • All 12 thread IDs preserved verbatim with severity + outcome class.
  • Drain-log shape matches existing docs/pr-preservation/*-drain-log.md template.

🤖 Generated with Claude Code

…sorb)

Otto-268 backfill: drain-log for PR #219 covering 12 threads
(7 FIX + 3 STALE-RESOLVED-BY-REALITY + 2 OTTO-279 SURFACE-CLASS).

Per Otto-250 training-signal discipline. Pattern observations capture
four load-bearing patterns:
1. External-source verifiability as a research-doc reproducibility
   discipline (URLs + arXiv IDs + DOIs are one-line-each but convert
   "grounded somewhere" into "reviewers can verify").
2. Inline-code-span line-wrap is the most-recurring formatting bug
   in this drain wave; pre-commit-lint candidate.
3. Otto-279 history-surface uniformity matured into a one-paragraph
   stamp reply for aurora-archive Attribution sections.
4. Phase-numbering / count-vs-surface-list cardinality findings
   recur across docs; future doc-lint candidate.
Copilot AI review requested due to automatic review settings April 25, 2026 06:55
@AceHack AceHack enabled auto-merge (squash) April 25, 2026 06:55
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a PR-preservation drain log for PR #219, capturing the resolution status of 12 review threads for the “Amara 3rd courier ferry” aurora absorb.

Changes:

  • Introduces docs/pr-preservation/219-drain-log.md with a thread-by-thread outcomes record.
  • Adds a short “pattern observations” section summarizing recurring review findings for training-signal value.

Comment thread docs/pr-preservation/219-drain-log.md
Comment thread docs/pr-preservation/219-drain-log.md Outdated
Copilot P2: prior summary 'sixth phase ... five phases total' read
as a contradiction. Reword to 'sixth phase ... after five existing
phases' so the drain-log doesn't record an impossible phase count.
@AceHack AceHack merged commit 81f6356 into main Apr 25, 2026
13 checks passed
@AceHack AceHack deleted the drain/219-pr-preservation-log branch April 25, 2026 08:08
AceHack added a commit that referenced this pull request Apr 25, 2026
…iated shape divergence (#467)

* hygiene(_patterns.md): document Otto-250-canonical vs Otto-268-abbreviated drain-log shape divergence

Multiple post-merge reviewer threads on the Otto-268-wave drain-logs
(#437-#465) flagged that the abbreviated inline shape doesn't match
the canonical Otto-250 multi-section format used in older drain-logs
(#108, #247, etc.). The findings are correct: the shapes ARE
different, and the abbreviated shape compresses verbatim
reviewer/reply text into short prose.

Documenting both shapes here in `_patterns.md` as a known
divergence + three maintainer-decision options:

(a) Rewrite — high churn, highest faithfulness.
(b) Accept divergence — document both as valid.
(c) Hybrid — canonical for substantive logs (math / crypto /
    algorithms / ADRs); abbreviated for low-substance.

Until maintainer decides, drain-runners writing future logs default
to canonical; existing Otto-268-wave logs stay abbreviated with
this known-divergence pointer.

This is the right place for the documentation per the synthesis-
over-history surface-class declaration: `_patterns.md` reflects
current corpus state including known shape divergences, separate
from the per-log records.

Composes with the per-PR drain-log threads currently flagging the
shape-conformance gap on #437/#441/#442/#444/#445/#446/#447/#449/
#460/#461/#464/#466 — those threads can now reply with a one-line
pointer to this section instead of repeating the maintainer-
decision-pending framing.

* hygiene(#467): fix 4 Copilot findings on shape-divergence section

Four Copilot catches converging on the same root cause: the
shape-divergence section was citing drain-log PR-numbers
(#437-#465) when readers will look for #437-drain-log.md etc.
and not find them — drain-log FILE numbers reference the
PRESERVED PR (e.g., #421/#422/#423), not the drain-log PR
itself. The current file corpus ends at #434.

Fixes:

- :374 + :394 — drop the misleading "#437-#465" PR-range citation;
  cite the actual in-repo abbreviated-shape examples
  (#421/#422/#423) by file path; drop the unsupported "22+"
  numeric estimate in favour of "the 2026-04-25 backfill wave".
- :380 — abbreviated template snippet now matches what the
  in-repo abbreviated logs actually use: `Finding:` bullet
  included, `Thread ID:` and `:LINE` placeholders dropped
  (those are canonical-shape fields, not abbreviated-shape).
  Reader can now copy/paste the template accurately.
- :388 — soften the "Substance is preserved" overstatement to
  the objective claim: key metadata (reviewer/severity/outcome/
  commit) is preserved; verbatim original-comment + verbatim
  reply text are NOT preserved; multi-section structure +
  file:line locator + Thread ID are also typically omitted.

The fixes are themselves Class A (count-vs-list cardinality on
"#437-#465" range) + truth-drift on a freshly-landed doc —
appropriate self-application of the discipline this section
documents.
AceHack added a commit that referenced this pull request Apr 25, 2026
Append-only row per Otto-229 discipline: drained 17 unresolved
threads across 8 of my own drain-log PRs (initial 13 + 4 cascade
findings on this drain wave's fixes). Documents the
'drain-log self-correction at scale' pattern — Codex/Copilot
reviews caught Class A/B pattern instances inside the same doc-lint
BACKLOG row that promotes them to lint candidates (appropriate
self-application).

PRs drained: #449 / #442 / #441 / #464 / #456 / #465 / #467 / #444.
Auto-merge SQUASH armed across the queue.

Cron f38fa487 minutely fire verified live throughout the tick.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants