Repository navigation
docs: simplify the mandatory host context - #162
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
1 participant
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.
The mandatory host context had grown to 25,079 bytes of repeated implementation and acceptance detail. Reduce it to 10,202 bytes, organized around current entrypoints, ownership, task-specific documentation and material unfinished boundaries. Preserve canonical checks, clean committed candidates, explicit registration and protected lifecycle requirements.
Correct the existing CI cache-adoption statement and host-context size record. Runtime, registrations and generated instruction roots are unchanged;
AGENTS.mdremains a relative symlink toCLAUDE.md.Validation: instruction generation succeeds with zero changes; all document targets resolve;
git diff --checkpasses. The committed candidate passes.chrono-harness/bin/chrono-harness check, selecting onlyinstructions-testsand running its registered format/build/test operations. Three independent review perspectives approve this bounded change. Shorter prose does not establish improved agent behavior or complete SPEC acceptance.