Release/0.1.8 - #12
Merged
Merged
Conversation
Stages 0.1.7 across the three sync points (package.json, package-lock, runtime VERSION in src/index.ts). Cut from main so PR #10 (e0827a8, array frameworkManifest normalization) is included -- the prior release branch did not contain it. Normalizer fix only. Extension stays 0.1.2 (separate vsce track).
.vscode/ is untracked developer convenience (extension-host launch + build task). It failed check:structure, the first gate in prepublishOnly, blocking local publish. The checker consults git check-ignore plus config/repository-structure.json; .vscodeignore governs vsce bundling only and has no bearing here. Kept separate from the 0.1.7 version bump.
The npm publish workflow asserted tarball contents by filename only, so a release could ship without the array-manifest normalizer and stay green. 0.1.5 and 0.1.6 both did exactly that (HAC-206). Extracts the packed tarball and greps dist/services/workspace.js for normalizeFrameworkManifest. Verified to discriminate: the published 0.1.6 tarball fails this check, a 0.1.7 pack passes it. Scope is deliberately narrow -- this is a presence check on a symbol. It catches the fix going missing, not the fix being wrong. A behavioural gate needs a non-empty frameworkManifest fixture, because an empty array normalizes to undefined with or without the fix and discriminates nothing. That fixture is the follow-up.
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.
Runtime correction
The audit found the inaccurate approval wording in two locations:
src/evidence.ts
src/tools/workspace.ts
Change both to a bounded statement:
Include the recorded co-change partners, or stop and review the exception with a human.
Add tests that prove:
missing evidenced partners still produce deny;
the message includes the new wording;
the message no longer includes get explicit human approval;
partner presence remains path-membership enforcement;
no override mechanism has been introduced.
Documentation correction
Complete the already drafted changes, but fix the additional mismatch the adversarial review identified:
Billfold uses one checkout/Stripe partner;
the local repository fixture walkthrough uses two partners.
Clearly label them as separate proof paths rather than describing both as the same example.
Also update:
hero wording;
remove unsupported A/B framing;
stale codex-demo-fixture links;
Billfold reproduction;
local versus provider network boundary;
path coverage versus semantic sufficiency;
current agents-audit producer name;
changelog.
Release