docs: one purpose per docs folder, lower-case names, archive point-in-time material - #264
Merged
Merged
Conversation
…posals and open plans, update references
This was referenced Sep 29, 2026
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
Implements Phase 1 and Phase 2 of the documentation taxonomy plan.
Validation
would move 123; 369 link(s) in 102 file(s); 259 mention line(s)ui-chrome-launchbecause this isolated worktree has noplaywrightdependencyPackage preview
npm pack --dry-runlists lower-case shipped docs and nodocs/evidence/paths.GitHub does not redirect renamed files, so older links to all-caps documentation URLs, including the shipped ak code reference, resolve only on older tags.
blob/mainlinks to the new paths resolve after merge.Phase 3 is intentionally sequenced after this merge on
docs/archive-link-repair.