Repository navigation
chore: enforce core boundaries and clarify maintainer workflows - #60
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
What changed
Make the evidence/authority boundary executable and easier to maintain. A dedicated core TypeScript project must pass diagnostics and produce an import inventory containing only contract/routing source, zod declarations, and standard libraries. This prevents host, UI, benchmark, and Node dependencies from entering the pure root. CI runs the guard, and
pnpm verifyprovides a single fail-fast local command.The development guide maps tasks to owning files/tests, traces comparison failures, explains measurement limits, and documents signed open-source delivery. README, AGENTS, CONTRIBUTING, llms.txt, architecture diagrams, roadmap, and SECURITY now point to the same workflow. SECURITY correctly distinguishes the pure package from optional live host adapters.
Memoize settled lessons and per-example history counts by their inputs, and preload the local body font. No measured latency or provider-savings claim is made.
Verdict impact
None. No model, question, fixture, decision table, receipt, or authorization semantics change. No dependency versions change.
Verification
pnpm verify(core boundaries, typecheck, offline tests, production build, secret patterns)The guard checks resolved imports and core diagnostics; it is not a runtime sandbox or proof of purity. Its regression covers unresolved Node imports that inventory-only compiler mode would miss. Human accessibility acceptance and live-provider smoke testing were not performed.