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

docs/BACKLOG.md

@@ -4275,6 +4275,8 @@ systems. This track claims the space.
 
 ## P2 — research-grade
 
+- [ ] **Pre-landing sanitizer for ferry absorbs — auto-clean Amara verbatim content before markdownlint CI.** Aaron 2026-04-24 Otto-119 directive: *"also we should backlog longer-term, a pre-landing sanitizer could handle this automatically."* Otto-118+119 observed systemic lint-triggering patterns in verbatim-preserved Amara ferry content: (1) `#<number>` at line-start parsed as H1 heading (MD018); (2) line-wrapped headings splitting a single `###` across two lines (MD001 heading-increment false positive); (3) lists without blanks-around (MD032); (4) trailing whitespace from tool-chain artifacts (MD009). Current pattern: per-ferry manual cleanup after markdownlint failures. Sanitizer automates this as pre-commit hook OR part of the courier-ferry-absorb skill. Scope: (1) catalog all observed lint-triggering patterns across PRs #311 / #312 / future ferries; (2) write sanitizer script (F#, Python, or shell — domain-appropriate) that auto-fixes mechanical patterns (wrap PR-number refs in backticks; unwrap headings split across lines; add blanks-around-lists; strip trailing whitespace); (3) integrate as pre-commit hook or courier-ferry-absorb skill step; (4) validate on existing ferries + future Otto-120+ absorbs. Priority P3 convenience (manual approach works; sanitizer saves 5-10 min per ferry). Effort S (pattern catalog + script) + S (integration). Composes with Otto-118 docs-lint policy + courier-ferry-absorb skill BACKLOG.
+
 - [ ] **Git-native PR-conversation preservation — extract PR review threads + comments to git-tracked files on merge.** Aaron 2026-04-24 Otto-113 directive: *"you probably need to resolve and save the conversations on the PRs to git for gitnative presevration"*. Currently PR review threads (Copilot / Codex connector / human reviewer comments) live GitHub-side only; if repo is mirrored / forked / GitHub has an outage / repo is migrated, the conversation substrate is lost. For glass-halo transparency + retractability, PR discussions belong in-repo. Proposed mechanism: workflow (or post-merge skill) that fetches all review threads + general PR comments for a merged PR, serialises them as markdown at `docs/pr-discussions/PR-<number>-<slug>.md` with attribution (reviewer id/bot), timestamps, thread structure, and resolution status. Scope: (1) design PR-discussion schema + file shape; (2) fetch-on-merge mechanism (GHA workflow using `gh api graphql`); (3) privacy pass (strip anything sensitive from reviewer comments); (4) backfill historical PRs or declare cutover-forward. Priority P2 research-grade; effort S (mechanism) + M (backfill if chosen). Composes with Otto-113 bootstrap-attempt-1 memory + docs-lint/memory-no-lint policy (discussions go in docs/) + the ChatGPT-download-skill (PR #300) pattern.
 
 - [ ] **Ongoing memory-sync mechanism — keep in-repo `memory/` mirrored with auto-memory writes during each Otto tick.** Aaron 2026-04-24 Otto-113 directive *"our memories should all be checked in now"* + Otto-114 confirmation that in-repo memory/ is the natural home for ALL memory types. Otto-113 one-shot sync (PR #307) mirrored 439 files. Going forward, every Otto tick that writes to `~/.claude/projects/.../memory/` should also land new/updated files in-repo `memory/` with matching MEMORY.md pointer update (per memory-index-integrity + memory-reference-existence-lint workflows). Proposed mechanisms: (a) end-of-tick skill that rsyncs new memories to a branch + PRs them; (b) direct-to-repo writes with auto-memory as read-cache; (c) GHA cron periodic sync. Initial preference: (a) for CLI-tool compatibility today, (b) long-term. Also includes path-unification design (decide whether to deprecate the `~/.claude/projects/...` path for this project entirely or keep as staging). Priority P2 research-grade; effort S (rsync skill) + M (direct-write tooling). Composes with `memory/feedback_natural_home_of_memories_is_in_repo_now_all_types_*.md` (Otto-114 policy) + PR #307 one-shot sync + memory-index-integrity workflow.