Add generic dynamic bundle + cronjob governance, policy env parity, and two-tier probe contracts#2
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.
Summary
GenericDynamicBundleso generic Hermes tools (starting withcronjob→HERMES_CRONJOB) register semantic-only action IDs fromIF_DYNAMIC_BUNDLE_MANIFESTat backend boot.cronjobto the governed catalog (mapper: generic), shipped policy/manifest/executor config, and adaptermap_genericpath.load_and_activate_pack()so CLIstart,integrate, and allpolicy *commands applyagent.jsonenv (including manifest path) before policy validation — fixespolicy reload hermesfailing with “allowed actionHERMES_CRONJOBhas no registered ActionBundle”.sync hermesCLI; dev hand-edits derived artifacts;test_actions_manifest.pygolden test enforces parity.Changes
Backend
GenericDynamicBundle+ manifest parser; wired intocore.yaml[native, dynamic]test_dynamic_bundle.pyexecutor.yamlincludesHERMES_CRONJOBHermes integration
tools.yaml:cronjob(mapper: generic,HERMES_CRONJOB)generic_actions.manifest,agent.json,policy.yamlupdatedmap_generic+ unit testCLI
integration_pack.py:apply_agent_env,seed_hermes_runtime_governance,load_and_activate_pack*policy_manage.pyandcli.pyroute through pack activationhermes_integrate.py/hermes_governance_contract.py: copy-only runtime seeding (never regenerate from yaml)Tests
test_actions_manifest.pytest_policy_manage.py,test_integration_pack.pytest_governed_tool_coverage.py, gateway E2E skipscronjobLLM probesgateway_e2e_probe_tool_names)test_cronjob_semanticin adapter + plugin gate suitesDocs
Test plan
./scripts/e2e.sh(unit + live adapter/plugin includingtest_cronjob_semantic)RUN_HERMES_GATEWAY_E2E=1 ./tests/scripts/test-hermes-gateway-e2e.sh(pass 1, 2a, 2b;cronjob=LIVE_SEMANTIC_ONLY)RUN_HERMES_GATEWAY_TOOLSETS=1 ./tests/scripts/test-hermes-gateway-toolsets.sh(schema probe fix for generic tools)uv run --package intentframe-integrations-cli python tests/intentframe_integrations/test_actions_manifest.pypolicy reload hermessmoke after integrate (no explicitIF_DYNAMIC_BUNDLE_MANIFESTexport)