Skip to content

hygiene(#268+): pr-preservation drain-log for #428 (#126 Gemini xref)#460

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

hygiene(#268+): pr-preservation drain-log for #428 (#126 Gemini xref)#460
AceHack merged 2 commits intomainfrom
drain/428-pr-preservation-log

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 25, 2026

Summary

Otto-268 follow-on: drain-log for PR #428 — targeted single-finding cascade follow-up to parent #126 (Grok CLI capability map). Captures one Gemini capability-map cross-reference truth-update.

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

Coverage

  • Gemini capability map xref truth-update (P2): cross-reference text updated to match current Gemini capability-map state; multi-CLI capability-map cluster needs joint cross-reference maintenance.

Pattern observations

  1. Cross-capability-map xref consistency is its own class. Repo has Codex / Grok / Gemini / Claude Code capability maps as a related-document cluster. Future doc-lint candidate: maintain manifest of related-document clusters; warn on edit-without-sweep.
  2. Multi-CLI capability-map family is its own substrate pattern. Shared structure (status taxonomy, parity-matrix shape, score-summary conventions) + joint cross-reference maintenance reduces drift.
  3. Targeted single-finding follow-ups are the cheapest cascade shape — cascade-pattern amortized cost is dominated by few-thread cascades.

Test plan

  • Finding preserved with severity + outcome class.
  • Multi-CLI capability-map cluster documented for future reference.
  • Drain-log shape matches existing docs/pr-preservation/*-drain-log.md template.

🤖 Generated with Claude Code

Copilot AI review requested due to automatic review settings April 25, 2026 07:21
@AceHack AceHack enabled auto-merge (squash) April 25, 2026 07:21
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6438efa2f3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/pr-preservation/428-drain-log.md Outdated
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 #428, capturing the post-merge follow-up thread about a Gemini capability-map cross-reference truth update and recording related pattern observations for the multi-CLI capability-map document cluster.

Changes:

  • Added docs/pr-preservation/428-drain-log.md documenting the drained thread(s) for PR #428.
  • Captured pattern observations about cross-capability-map xref drift and cluster maintenance.

Comment thread docs/pr-preservation/428-drain-log.md Outdated
Comment thread docs/pr-preservation/428-drain-log.md Outdated
AceHack added 2 commits April 25, 2026 03:58
…mini xref)

Otto-268 follow-on: drain-log for the targeted single-finding cascade
PR #428 (post-merge follow-up to parent #126 Grok CLI capability map).
Captures one Gemini capability-map cross-reference truth-update.

Per Otto-250 training-signal discipline. Pattern observations:

1. Cross-capability-map xref consistency is its own class. The repo
   has a growing family of CLI capability maps (Codex / Grok /
   Gemini / Claude Code) that form a related-document cluster
   needing joint cross-reference maintenance. Future doc-lint
   candidate: maintain manifest of related-document clusters and
   warn on edit-without-sweep.

2. Multi-CLI capability-map family is its own substrate pattern.
   Worth documenting in `_patterns.md`: when multiple capability
   maps cover overlapping but distinct CLIs, they form a cluster
   that benefits from shared structure (status taxonomy, parity-
   matrix shape, score-summary conventions) and joint
   cross-reference maintenance.

3. Targeted single-finding follow-ups are the cheapest cascade
   shape — 1 finding / 1 commit / 1 merge gate. Cascade-pattern
   amortized cost is dominated by the few-thread cascades.

URL → PR-number defensive pattern continues (lesson from #454/#455
collision earlier this session).
Codex P2 + Copilot P1+P2 caught:

- Inline code span split across newline (`docs/` on one line,
  `research/openai-codex-cli-capability-map.md` on the next) —
  reflowed to single-line so the path renders as one token.
- Capability-map cluster listed `docs/research/codex-cli-first-
  class-2026-04-23.md` as if in-tree, but PR #231 is still OPEN
  at time of this drain-log so the file isn't yet in main.
  Reframed as 'pending merge of PR #231; will be in-tree once
  that PR lands' with the in-tree
  `openai-codex-cli-capability-map.md` listed first.

Same forward-author-to-future-state-of-main drift class as #377
(38% stale-resolved density). The drain-log itself exhibits the
pattern it documents — cited a forthcoming-but-not-yet-landed
file as if already present.

Inline-code-span line-wrap is the 5th observation of that class
in the corpus (now: #191 / #195 / #219 / #423 / #460). At this
density the doc-lint Class A (PR #465 BACKLOG) is high-leverage
automation.
@AceHack AceHack force-pushed the drain/428-pr-preservation-log branch from 6438efa to 66575b7 Compare April 25, 2026 07:58
@AceHack AceHack merged commit d10d6e3 into main Apr 25, 2026
13 checks passed
@AceHack AceHack deleted the drain/428-pr-preservation-log branch April 25, 2026 08:00
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.
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