chore: drop nonexistent examples entry from package.json files#19
Merged
Conversation
The `examples/` entry referenced a directory that does not exist (npm silently omitted it). The originally-planned examples were Helio *policy* files (personal/team.helio.yaml), which belong to the main Helio project, not this policy-agnostic adapter — the adapter's own config (incl. evidence rules) is documented in the README. Removing the dangling entry; the published tarball is unchanged.
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.
package.jsonfileslistedexamples, but noexamples/directory exists — npm silently omitted it (dangling entry).The originally-planned artifacts (plan B.1) were
examples/{personal,team}.helio.yaml— Helio policy files, which belong to the main Helio project, not this adapter. This package is a pure translator with no policy logic, so shipping policy examples here would duplicate/drift and blur that boundary. The adapter's own configuration (incl. evidence-extraction rules) is already documented in the README'sConfigure/Grounding evidencesections.Removing the dangling entry. The published tarball is unchanged (still 8 files) — this is pure tidy-up. The implementation plan (gitignored) has been annotated with the same rationale.
pnpm verify/npm pack --dry-runconfirmed clean.