Skip to content

shard(tick): 2131Z — PR #3256 plus-at-line-start fix (Copilot review)#3262

Merged
AceHack merged 1 commit into
mainfrom
shard/tick-2131Z-pr3256-plus-linestart-fix-otto-cli-2026-05-14
May 14, 2026
Merged

shard(tick): 2131Z — PR #3256 plus-at-line-start fix (Copilot review)#3262
AceHack merged 1 commit into
mainfrom
shard/tick-2131Z-pr3256-plus-linestart-fix-otto-cli-2026-05-14

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented May 14, 2026

Summary

Tick 2026-05-14T21:31Z shard. Substantive work was a thread fix on #3256: Copilot caught a wrapped continuation line starting with + inside a - bullet — markdownlint parses that as a new list item with a different bullet style.

What landed

  • Commit 9c4590e on PR #3256's branch — rewrote the wrapped continuation as prose so no line starts with +. Thread resolved.
  • This shard.

Repo has dedicated audit for this class

The fix used tools/hygiene/audit-md032-plus-linestart.ts for the proactive sweep — empty result across all today's shards after the fix.

Pre-push catch

Pre-lint of this shard caught a fresh MD018 (ATX-heading-missing-space): line starting with #3256. parsed as an ATX heading missing a space. Prefixed with PR so the line doesn't start with #. Cheap pre-push lint catches it before CI.

Pattern codified

When authoring tick shards with structured content (bulleted descriptions of file sections), use plain prose for the description rather than +-separated lists inside existing - bullets. Also avoid #NNN at line start when referencing PRs — prefix with PR .

Test plan

  • markdownlint-cli2 clean on the fixed 2123Z shard
  • markdownlint-cli2 clean on this shard
  • audit-md032-plus-linestart --list empty across today's shards
  • Thread resolved via GraphQL
  • Composite branch-guard + gh pr create --head used
  • CI clears
  • Auto-merge

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

Tick output:
- Commit 9c4590e on PR #3256 branch: rewrote wrapped continuation
  starting with `+` as prose. The leading `+` was parsing as a new
  list item with a different bullet style. Repo has a dedicated audit
  (audit-md032-plus-linestart.ts) for this class.
- This shard.

Pattern codified: when authoring tick shards with structured content
(bulleted descriptions of file sections), use plain prose for the
description rather than `+`-separated lists inside existing `-` bullets.

Proactive sweep: audit-md032-plus-linestart --list on today's shards
returns empty after the fix.

Also caught pre-push: line starting with `#3256.` tripped MD018
(ATX-heading-missing-space). Prefixed with "PR " so the line doesn't
start with `#`. Cheap pre-push lint catches the hazard before CI.

Cron sentinel 12fb713e armed; recurring.

Co-Authored-By: Claude <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 14, 2026 21:34
@AceHack AceHack enabled auto-merge (squash) May 14, 2026 21:34
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

This PR adds a single tick-shard markdown file documenting work performed in tick 2026-05-14T21:31Z: addressing a Copilot review finding on PR #3256 about a wrapped continuation line starting with + inside a - bullet (markdownlint hazard), plus a proactive sweep using the repo's dedicated audit tool.

Changes:

  • New hygiene-history tick shard recording the +-at-line-start fix and resolution of the Copilot thread on PR #3256.
  • Documents the dual-audit pattern (audit-md032-plus-linestart.ts + markdownlint-cli2) for future shard authoring.

@AceHack AceHack merged commit 724c9a2 into main May 14, 2026
25 checks passed
@AceHack AceHack deleted the shard/tick-2131Z-pr3256-plus-linestart-fix-otto-cli-2026-05-14 branch May 14, 2026 21:36
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