Repository navigation
chore(quality): align the extension docs and cover the push routes - #24
Merged
Merged
Conversation
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.
Why
A quality pass over
oh-my-pocketfound two documents that no longer matched the code, and one user-facing route group with no test. The extension docs drifted as modules were added, and the push routes were untested.What changed
docs/map.mdlists every built-in extension in install order, includingrouters,read-economy,loop-guard,pruner,tool-repair, andtoday.docs/extensions.mdnames the host members a drop-in can use, includingenvFor,routerFor,loopGuard,pip,pipCompaction, andpruner.test/push-routes.test.tscovers the/api/pushroutes, the largest untested gap among core server modules.docs/triage-2026-10-16.mdrecords where the 20 open upstream issues stand for this fork.Scope
This covers docs accuracy, one new test file, and a triage note. It leaves the code alone and adds no dependencies. The README's battery test counts and its extensions summary row are left as they are.
Blast radius
Docs and one new test file. Nothing under
src/orweb/changes, so no running server is affected.Verification
npm testpasses 643 of 643 tests, including the 3 new ones.npm run check,npm run lint, andnpm run check:webpass.node --test test/push-routes.test.tspasses 3 of 3.npx prettier --checkpasses on every changed file. The fullnpm run format:checkwarns on an untrackedopencode.jsonthat this worktree holds and the repository does not.