feat(test): run the CLI test runner under a declared root security scope - #107
Merged
Conversation
The runner discovers and executes arbitrary registry entries, so it declares meta.command.security with its own actor and an unrestricted runner_policy. The CLI launcher (wippyai/runtime#558) resolves the block and installs the context at start, which restores test discovery under strict security mode — previously the actor-less runner process had every registry read denied and reported 'No tests found'.
wolfy-j
force-pushed
the
feat/test-runner-command-security
branch
from
August 8, 2026 00:36
8e27599 to
04bafc7
Compare
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.
Companion to wippyai/runtime#558.
The test runner discovers and executes arbitrary registry entries, so it needs an unrestricted scope; the CLI launcher installing it is the trust anchor (the operator started
wippy run teston their own deployment).wippy.test:runner_policy— allow-all security.policy owned by the module.wippy.test:runner— declaresmeta.command.security(actorwippy.test:runner, policyrunner_policy), which the patched CLI resolves and installs at launch.Under strict security mode (default since runtime v0.3.27a) the actor-less runner had every registry read denied and reported No tests found on every module harness. With runtime#558 + this change, the kickside-module template harness discovers and passes its full suite with strict mode on (verified E2E; stock CLI on the same tree still fails, proving the launcher change is the enabling piece).
On CLIs without runtime#558 the extra meta and policy entry are inert; behavior is unchanged. Needs a wippy/test republish once merged.