Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 30 additions & 12 deletions .markdownlint-cli2.jsonc
Original file line number Diff line number Diff line change
Expand Up @@ -76,18 +76,36 @@
// archive, the transfer-report which has its own lint-compliance
// carve-out, etc.) stay linted.
"docs/aurora/2026-*-amara-*.md",
// Same verbatim-ferry pattern as `docs/aurora/2026-*-amara-*.md`
// but for ferries that landed under `docs/research/` instead of
// `docs/aurora/` (the directory split happened mid-stream as the
// Amara absorb cadence formalised; older absorbs went to
// `docs/research/`, newer ones to `docs/aurora/`). Same Otto-227
// signal-in-signal-out rationale: the body is verbatim Amara
// output and reformatting MD027 multi-space-blockquote /
// MD032 blanks-around-lists / MD029 ol-prefix would alter the
// courier-protocol content. Scoped to the named ferry-absorb
// pattern only; non-Amara, non-ferry docs under `docs/research/`
// stay linted.
"docs/research/2026-*-amara-*.md"
// Verbatim-ferry preservation under `docs/research/` for any
// ferry source (Amara, Gemini, Grok, Codex, Aaron-quoted, etc.)
// landing as a date-stamped absorb file. Original carve-out was
// `docs/research/2026-*-amara-*.md` which only covered Amara
// ferries; PR #19 (gemini-deep-think + action-mode verbatim
// Aaron-quote files) exposed the Amara-only scoping as too
// narrow.
Comment on lines +79 to +85
Copy link

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

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

This new comment block introduces personal-name attribution on a current-state config surface (e.g., “Aaron-quoted”, “Aaron-quote files”). Repo guidance is to use role references outside the history-surface paths (see docs/AGENT-BEST-PRACTICES.md:284-325). Consider rewriting these references to role-refs (e.g., “human-maintainer-quoted”) to stay consistent with that convention.

Copilot uses AI. Check for mistakes.
//
// Repo convention: files in `docs/research/` with the
// `2026-MM-DD-<source-or-topic>-...md` date-PREFIX shape are
// verbatim courier-protocol absorbs; they carry "## Verbatim
// preservation" sections + GOVERNANCE §33 archive headers
// (Scope / Attribution / Operational status: research-grade /
// Non-fusion disclaimer). Author-controlled research docs use
// non-date-prefixed names (e.g. `actor-model-*.md`,
// `agent-cadence-log.md`) or date-SUFFIXED names (e.g.
// `aaron-knative-...-2026-04-21.md`) — date-prefix vs
// date-suffix is the discriminator.
Comment on lines +89 to +96
Copy link

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

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

The comment says date-prefixed docs/research/ absorbs “carry "## Verbatim preservation" sections”, but a repo-wide search shows no Verbatim preservation heading/text under docs/research/** (it exists under docs/aurora/**). This makes the rationale misleading; consider rewording to point at the actual invariant these files share (e.g., the GOVERNANCE §33 boundary header/frontmatter + verbatim blocks), rather than a section title that doesn’t exist here.

Suggested change
// verbatim courier-protocol absorbs; they carry "## Verbatim
// preservation" sections + GOVERNANCE §33 archive headers
// (Scope / Attribution / Operational status: research-grade /
// Non-fusion disclaimer). Author-controlled research docs use
// non-date-prefixed names (e.g. `actor-model-*.md`,
// `agent-cadence-log.md`) or date-SUFFIXED names (e.g.
// `aaron-knative-...-2026-04-21.md`) — date-prefix vs
// date-suffix is the discriminator.
// verbatim courier-protocol absorbs; they carry the
// GOVERNANCE §33 archive boundary/frontmatter
// (Scope / Attribution / Operational status: research-grade /
// Non-fusion disclaimer) plus verbatim preserved blocks.
// Author-controlled research docs use non-date-prefixed names
// (e.g. `actor-model-*.md`, `agent-cadence-log.md`) or
// date-SUFFIXED names (e.g. `aaron-knative-...-2026-04-21.md`)
// — date-prefix vs date-suffix is the discriminator.

Copilot uses AI. Check for mistakes.
//
// Same Otto-227 signal-in-signal-out rationale as the aurora
// carve-out: the body is verbatim ferry output and
// reformatting MD027 / MD032 / MD029 would alter
// courier-protocol content. Pattern is broader than the
// amara-only original — covers any ferry source via the
// date-prefix convention. Trade-off: a non-ferry
// author-controlled doc that accidentally lands with
// date-prefix shape would skip lint; the cost of that miss is
// small (research docs are markdown only) compared to the
// cost of churning verbatim ferry content.
"docs/research/2026-*-*.md"
Copy link

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

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

The ignore glob docs/research/2026-*-*.md is broader than the documented “2026-MM-DD-... date-PREFIX” discriminator: it will also match filenames like 2026-04-topic.md (year-month) if any are added later. To keep the carve-out scoped to full dates as intended, use a pattern that encodes the day as well (e.g., 2026-??-??-*.md or an equivalent digit-class glob supported by markdownlint-cli2).

Suggested change
"docs/research/2026-*-*.md"
"docs/research/2026-??-??-*.md"

Copilot uses AI. Check for mistakes.
],
"noBanner": true,
"noProgress": true,
Expand Down