Skip to content

backlog: pre-landing sanitizer for ferry lint (Aaron Otto-119)#313

Closed
AceHack wants to merge 1 commit intomainfrom
backlog/pre-landing-sanitizer-for-ferry-lint
Closed

backlog: pre-landing sanitizer for ferry lint (Aaron Otto-119)#313
AceHack wants to merge 1 commit intomainfrom
backlog/pre-landing-sanitizer-for-ferry-lint

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 24, 2026

Files Aaron Otto-119 directive 'we should backlog longer-term, a pre-landing sanitizer could handle this automatically.' Captures the Otto-118+119 observed pattern.

🤖 Generated with Claude Code

Copilot AI review requested due to automatic review settings April 24, 2026 07:01
@AceHack AceHack enabled auto-merge (squash) April 24, 2026 07:01
@chatgpt-codex-connector
Copy link
Copy Markdown

chatgpt-codex-connector Bot commented Apr 24, 2026

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

@AceHack AceHack force-pushed the backlog/pre-landing-sanitizer-for-ferry-lint branch from bec3f90 to 62a2ce3 Compare April 24, 2026 07:02
Copilot AI reviewed Apr 24, 2026
View reviewed changes
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 new backlog item capturing the idea of an automated “pre-landing sanitizer” to mechanically fix recurring markdownlint-trigger patterns observed when absorbing Amara ferry content, reducing manual cleanup after CI failures.

Changes:

  • Add a P2-section backlog entry proposing an auto-sanitizer (script + integration hook/skill step) for common markdownlint-triggering patterns.
  • Document the initial scope, candidate fixes, and integration points for the sanitizer.

Comment thread docs/BACKLOG.md
Comment thread docs/BACKLOG.md
Comment thread docs/BACKLOG.md
@AceHack AceHack force-pushed the backlog/pre-landing-sanitizer-for-ferry-lint branch from 62a2ce3 to 7ec5478 Compare April 24, 2026 07:13
Copilot AI review requested due to automatic review settings April 24, 2026 07:23
@AceHack AceHack force-pushed the backlog/pre-landing-sanitizer-for-ferry-lint branch from 7ec5478 to 0f0cc55 Compare April 24, 2026 07:23
@AceHack @claude
backlog: pre-landing sanitizer for ferry lint (Aaron Otto-119)
81adecd 
Filed per Aaron Otto-119 closing directive: 'also we should
backlog longer-term, a pre-landing sanitizer could handle this
automatically.'

Captures systemic lint-triggering patterns observed Otto-118+119
in verbatim-preserved Amara ferry content: line-start #<number>
→ H1 mis-parse; line-wrapped headings; missing blanks-around-
lists; trailing whitespace. Current manual per-ferry cleanup
pattern works; sanitizer automates.

P3 convenience; S+S effort.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@AceHack AceHack force-pushed the backlog/pre-landing-sanitizer-for-ferry-lint branch from 0f0cc55 to 81adecd Compare April 24, 2026 07:26
Copilot AI reviewed Apr 24, 2026
View reviewed changes
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

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

@AceHack
Copy link
Copy Markdown
Member Author

AceHack commented Apr 24, 2026

Superseded by consolidated resurrect (PR to follow). Positional-rebase-conflict pattern — same as #319/#322 closure.

@AceHack AceHack closed this Apr 24, 2026
auto-merge was automatically disabled April 24, 2026 07:48

Pull request was closed

AceHack added a commit that referenced this pull request Apr 24, 2026
@AceHack @claude
backlog: resurrect 3 BACKLOG rows consolidated (supersedes #313 + #314 …
f6695a7 
…+ #320)

PRs #313 (pre-landing sanitizer), #314 (claude --agent flag research),
and #320 (schema-as-graph) all hit DIRTY state from positional
rebase conflicts — each added a row at top of P2, but successive
merges of adjacent BACKLOG PRs kept moving the P2 top anchor. Each
branch's append collided with main's now-different top.

Closed all three and re-filed in a single consolidated PR above
the KSK-naming row. Order chosen by directive date:
1. Schema-as-Graph (Otto-127, most recent)
2. Research claude --agent flag (Otto-120)
3. Pre-landing sanitizer (Otto-119)

Superseded PRs:
- #313 backlog/pre-landing-sanitizer-for-ferry-lint
- #314 backlog/claude-cli-agent-flag-research-map
- #320 backlog/graph-as-schema-first-class-entities

Content preserved + condensed in this PR.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack added a commit that referenced this pull request Apr 24, 2026
@AceHack @claude
backlog: resurrect 3 BACKLOG rows consolidated (supersedes #313 #314 #…
1aa4056 
…320) (#325)

* backlog: resurrect 3 BACKLOG rows consolidated (supersedes #313 + #314 + #320)

PRs #313 (pre-landing sanitizer), #314 (claude --agent flag research),
and #320 (schema-as-graph) all hit DIRTY state from positional
rebase conflicts — each added a row at top of P2, but successive
merges of adjacent BACKLOG PRs kept moving the P2 top anchor. Each
branch's append collided with main's now-different top.

Closed all three and re-filed in a single consolidated PR above
the KSK-naming row. Order chosen by directive date:
1. Schema-as-Graph (Otto-127, most recent)
2. Research claude --agent flag (Otto-120)
3. Pre-landing sanitizer (Otto-119)

Superseded PRs:
- #313 backlog/pre-landing-sanitizer-for-ferry-lint
- #314 backlog/claude-cli-agent-flag-research-map
- #320 backlog/graph-as-schema-first-class-entities

Content preserved + condensed in this PR.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(#325): 2 review threads — priority/section alignment + <agent_name> inline-code escape

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
@AceHack AceHack reopened this Apr 24, 2026
@AceHack
Copy link
Copy Markdown
Member Author

AceHack commented Apr 24, 2026

Reopening per 2026-04-24 closed-PR audit (maintainer directive to recover over-closes). This PR captured an Aaron directive into docs/BACKLOG.md row(s); content is NOT on main through any other path; closure was part of my over-close cascade.

Status note: this PR adds rows to docs/BACKLOG.md. Per HB-002 blocker (per-row-BACKLOG migration pending), new flat-file BACKLOG.md rows are on hold. This PR sits open as a recovery landing point:

  • If maintainer wants the content landed as-is pre-split, override the HB-002 hold for this PR specifically.
  • Post per-row-BACKLOG split lands, the row(s) convert to per-row files and this PR can merge via the new substrate.
  • Either way, content is preserved and visible, not lost in a silent close.

Retractability-in-action per Otto-238: visible reopen; no silent reversal.

@AceHack
Copy link
Copy Markdown
Member Author

AceHack commented Apr 24, 2026

Re-closing — my earlier reopen was a false recovery. Audit of docs/BACKLOG.md shows this row's content is already on main via a different PR landing path (Otto-120 content found 2× on main, Otto-119 found 1×, Otto-139..149 found 3× among the multi-directive's rows). The content is NOT lost; merging this PR would create a duplicate row.

Maintainer flagged queue saturation (73 open PRs on LFG). Re-closing false-recovery reopens drops the count without losing content. Per retractability-in-action (Otto-238): visible re-close with rationale, not silent delete.

If any specific row from this PR needs recovery that I missed in the audit, reopen again with a pointer to the missing content.

@AceHack AceHack closed this Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@AceHack