fix(runtime): validate AgentProlog profile advertisement set #37
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
security
testing
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/agentProlog!37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/zara-profile-closed-set"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Tighten the optional AgentProlog profile boundary for lost-rob0t/zara#1046 S5.
Prolog-RLM remains the runtime authority and AgentProlog remains a downstream profile. The adapter no longer projects
agentprologfrom a malformedprofilesdescriptor merely because the array happens to contain the target string.RED-first
0d01f8a6b52a883898aaa5905197e681750f64e3adds the regression first. The exact-headZara Runtime Profileworkflow failed as expected.172efc99d57078e80fed0ebc8493b90ecb652c65implements closed-set validation.Coverage rejects profile arrays containing null/empty/control-bearing identities and duplicate profile identities, while still allowing another well-formed profile alongside
agentprolog.Boundary
The change is limited to the AgentProlog profile validator and tests. It adds no runtime registry, provider/model/planner authority, Zara dependency, or dependency reversal. AgentProlog remains an optional profile over
prolog-rlm.Exact-head evidence
At
172efc99d57078e80fed0ebc8493b90ecb652c65:Zara Runtime Profile: SUCCESSCI: SUCCESS (flake check, default-package build, default-app run)main@140f4f0091ffe6f933994fd89ab25276c6166309Refs lost-rob0t/zara#1046.
Pull request closed