Repository navigation
test(skills): retain hello world until index refresh - #173
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
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.
Publish a one-file Hello world probe at the existing standalone
callesource so the owner can observe when skills.sh indexes the changed contents and then inspect the Snyk report. This follow-up explicitly keeps the probe online; there is no automatic restoration deadline.The unique marker is
calle-index-probe-20261028-persistent-hello-world. The complete 19-file 2.0.1 source is backed up with hashes. Immutable release tags and assets, CLI compatibility, plugin packages, tests and CI remain unchanged.The official Skill format validator and one-file ZIP packaging validate this diagnostic payload. Production workflow tests are expected to fail while those workflow resources are intentionally absent, as established in #171; no tests or CI rules are weakened. Monitoring separately verifies public source, skills.sh body and Snyk report freshness. A successful installation does not confirm registry refresh, and a new audit timestamp alone does not identify the scanned source revision.
Release decision: No release needed for npm/plugin packages. This is an explicitly authorized source-only diagnostic, not a new normal product release; no changeset or immutable release artifact is created. PR history records the temporary public behavior.