Skip to content

fix: Trial 2 lessons; release 0.4.1 - #12

Merged
jisujit merged 1 commit into
devfrom
fix/0.4.1
Nov 14, 2026
Merged

jisujit merged 1 commit into
devfrom
fix/0.4.1

Conversation

@jisujit

@jisujit jisujit commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Fixes from Trial 2 (DESIGN §10, "Trial 2 result").

  • move lists links that name a moved doc by its full address (a GitHub URL to the repo's own file, file:///) under REVIEW (hazard H13). It does not rewrite them.
  • init adds a protected doc at the docs root to rootAllowed, so the check can pass without moving it.
  • init warns when the repo uses Biome, which rejects the comments in docs-kit.json.
  • check: the exports error says an exports/ folder is not allowed, instead of reading as if it were missing.
  • /docs-kit-reorg: generator slice before the moves, largest move last; keeps folders that hold a protected doc; never lists archive as a subject; gives each kept doc a reason ("cannot move" or "kept by choice"); tells the owner which code files changed only in a doc path, because a doc-sync gate may report them.

Not here: the doc-sync gate's false positive on path-only comment changes. That fix belongs in govkit.

Tests: 133 pass. Each new guard was broken on purpose and a test caught it.

🤖 Generated with Claude Code

- move: list links that name a moved doc by full address (a URL or
  file:///) for review (hazard H13)
- init: allow a protected doc at the docs root in rootAllowed; warn when
  Biome would reject the comments in docs-kit.json
- check: the exports error says an exports/ folder is not allowed
- /docs-kit-reorg: generators before moves; keep folders that hold a
  protected doc; archive is never a subject; "cannot move" vs "kept by
  choice"; tell the owner about code files changed only in a doc path
- DESIGN: H13, move step 10, Trial 2 result

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Sujit Gangadharan <gsujit@gmail.com>
@jisujit
jisujit merged commit 426cc8f into dev Nov 14, 2026
3 checks passed
@jisujit jisujit mentioned this pull request Nov 14, 2026
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.

1 participant