Pinning is opt in - #7
Merged
Merged
Conversation
devia init copied the whole standard into .devia/standard/. Measured on a real repository: 391 pinned files against 17 of memory. A folder whose purpose is to be read was 96% a copy nobody wrote; on a 211-file project it tripled the repository, and every sync produced a 391-file diff in which a real memory change was invisible. - init writes the memory and the adapters and pins nothing: 17 files, 57 kB - init --vendor pins the copy up front for those who want it - sync pins on demand and refreshes afterwards: that is now its first job - doctor reports an unpinned standard as INFO, not a WARN to clear. The default is not a defect, and a permanent warning teaches people to ignore the output - The memory templates, the agent adapters and the skill now read the rules with `devia rules --id <ID>` / `--domain <name>` instead of linking into a copy that may not exist. A pinned copy is described as what it is: optional The new test caught two things while being written: templates/project/AGENTS.md still linked into standard/, and the sync test only passed because init used to pin. Both were the same class of bug the change is about -- a document asserting a file that is not there. Upgrading needs nothing. An existing .devia/standard/ is untouched, sync keeps refreshing it, only new init runs differ. Recorded as G8 with the measurement. Version: package 0.5.0, standard unchanged at 0.1.0. Verified: 35 tests with and without FORCE_COLOR, including one that asserts init pins nothing, that no memory file links into a standard nobody pinned, and that doctor reports the absence without a warning.
MEM-DEBT-P0 matched P0 anywhere in a debt row, prose included. Writing a real project's debt registry produced the line "becomes P0 once the payment module ships" at priority P1, and the gate reported a P0 blocker on a project that had none. A P0 FAIL that is not true is worse than a missing check: it is the one result nobody is allowed to ignore. The priority is a cell. The check now reads it as one.
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.
Summary
Type
Devia compliance
.devia/layout, CLI contract):CHANGELOG.mdupdated:npm run build:index):Checks
npm run validatepassesnpm testpassesnode bin/devia.mjs check --root .passesdevia initstill produces a valid project (devia validateclean in a scratch repo)Not verified