Conversation
There was a problem hiding this comment.
Pull request overview
Adds two new P3 per-row backlog entries capturing (1) a recurring hygiene/tooling gap around markdownlint performance due to missing repo-aware exclusions, and (2) a terminology/naming clarity issue where “upstream” is being used colloquially for references/ content and collides with git semantics.
Changes:
- Add backlog row B-0030 proposing a Bun/TypeScript wrapper tool for markdownlint with canonical exclusions (motivated by measured runtime cost).
- Add backlog row B-0031 proposing an audit + glossary clarification/sweep to disentangle “upstream” (git meaning) vs
references/(vendored/mirrored material) vocabulary.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| docs/backlog/P3/B-0030-lint-with-exclusions-tool-typescript-otto-346-fourth-violation-with-real-cost.md | New backlog row documenting need for a TS lint wrapper with repo-aware exclusions and cost evidence. |
| docs/backlog/P3/B-0031-rename-references-directory-naming-clarity-avoid-upstream-collision-aaron-2026-04-26.md | New backlog row documenting the “upstream” terminology collision and proposing an audit/glossary-driven fix. |
…ith real cost) + references/ naming-clarity rectify (Aaron 2026-04-26) Aaron 2026-04-26 caught two distinct concerns in one message: (1) **Otto-346 violation #4 with real cost** — bash pipeline `markdownlint-cli2 "**/*.md" | grep -E 'MD[0-9]{3}'` lacked repo-aware exclusions, ran ~60s instead of ~3s (20x penalty per invocation). Same recurring-pattern Otto-346 names; this one differentiated by measurable cost. B-0030 captures the tool extraction (TS target per B-0015 P2): - Wrap markdownlint-cli2 with repo-aware default exclusions - Reads exclusion config from `.markdownlint-cli2.jsonc` - Cost reduction: 60s → 3s (20x) Cumulative Otto-346 violation count this session: FOUR. The discipline keeps slipping per-instance; the cumulative count IS the signal that B-0015 sibling-migration unblock should happen now, not later. (2) **"upstream" naming collision** — Aaron self-corrected: he'd been using "upstream" colloquially to refer to references/ directory contents (vendored mirrors), but "upstream" has specific git-semantic meaning. Two different meanings, same word, recipe for confusion. B-0031 captures the rectify: - Audit current "upstream" usage across docs/memory/tools - Distinguish git-correct from colloquial uses - Define replacement vocabulary for colloquial sense - Update docs/GLOSSARY.md - Sweep substrate Aaron's framing in same message: "people literraly say your programming laganguage choice is like a religious choice, and there are programming language wars that resemble religious wars" — composes with the naming-discipline at meta-level: vocabulary collisions create religious-war pattern at substrate-naming layer. Otto-286 (definitional precision changes future without war) is preventive against this. Both rows compose with: Otto-346 (dependency symbiosis upstream-contribution discipline; the colloquial conflation contaminates Otto-346's precision), Otto-339 (anywhere-means-anywhere; vocabulary precision applies to directory/concept naming), Otto-286 (definitional precision without war), B-0010 (memory-index-conventions sibling naming-discipline), B-0015 (TS-migration P2; B-0030's TS target follows). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
AceHack
force-pushed
the
backlog/B-0030-B-0031-lint-with-exclusions-tool-plus-references-dir-rename-from-aaron-lint-cost-observation
branch
from
a173ddb to
3dd40c9
Compare
There was a problem hiding this comment.
Pull request overview
Adds two new backlog rows capturing (1) the need for a repo-aware markdownlint wrapper tool (TS/Bun target) with directory exclusions to avoid expensive runs, and (2) a naming/vocabulary clarification to avoid conflating “upstream” (git semantic) with references/ (mirrored/vendored content).
Changes:
- Add backlog row B-0030 describing a TypeScript
lint-md-with-exclusionstool to canonicalize markdownlint exclusions (speed/cost motivation). - Add backlog row B-0031 describing an audit + glossary/vocabulary sweep to prevent “upstream” naming collisions around
references/.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/backlog/P3/B-0030-lint-with-exclusions-tool-typescript-otto-346-fourth-violation-with-real-cost.md | New backlog row for extracting a TS markdownlint wrapper with repo-aware exclusions. |
| docs/backlog/P3/B-0031-rename-references-directory-naming-clarity-avoid-upstream-collision-aaron-2026-04-26.md | New backlog row for clarifying/replacing colloquial “upstream” usage and updating glossary/sweep. |
AceHack
deleted the
backlog/B-0030-B-0031-lint-with-exclusions-tool-plus-references-dir-rename-from-aaron-lint-cost-observation
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aaron 2026-04-26 caught two distinct concerns in one message:
B-0030 — Otto-346 violation #4 with REAL COST
Bash pipeline
markdownlint-cli2 \"**/*.md\" | grep -E 'MD[0-9]{3}'lacked repo-aware exclusions, ran ~60s instead of ~3s. 20x cost penalty per invocation; differentiated from prior Otto-346 catches by measurable cost-evidence.Tool target:
tools/hygiene/lint-md-with-exclusions.ts(TypeScript per B-0015 P2 priority bump).B-0031 — "upstream" naming collision
Aaron self-corrected: "upstream" used colloquially for
references/directory contents collides with git-semantic meaning. Two different concepts, same word, recipe for confusion.Captures the audit + replacement-vocabulary work + glossary update + sweep.
Cumulative Otto-346 violations this session: FOUR
The cumulative count IS the signal: B-0015 sibling-migration unblock should happen now, not later.
Programming-language-as-religious-choice connection
Aaron's same message: "people literraly say your programming laganguage choice is like a religious choice, and there are programming language wars that resemble religious wars"
Composes with B-0031 naming-discipline at meta-level: vocabulary collisions create religious-war pattern at substrate-naming layer that programming-language choice creates at implementation layer. Otto-286 (definitional precision changes future without war) is preventive against this.
Composes with
docs/GLOSSARY.md(target for B-0031 formal distinction)Test plan
🤖 Generated with Claude Code