Repository navigation
Enforce the dependency namespace boundary with composition disabled #268
Description
🤖 Generated by the Agentic Engineer
Part of #1. This delivery does not retire an adoption or release gate.
Evidence and audience
The ordinary dependency lookup accepts a foreign namespace while composition is disabled, although the published contract requires every edge to remain in the consumer namespace. This affects product authors and consumers using the documented workflow.
Intended outcome
Make the declared workflow reliable without widening source access or moving data or credentials into controller metadata. A focused failing regression is the acceptance proxy; implementation tests do not establish independent production adoption.
Acceptance criteria
- Reject foreign references before any producer read in both composition states.
- Retain healthy same-namespace dependency behavior and stable public denial messages.
- Keep graph evaluation and lineage disabled when their release gate is off.
Rough size: S.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
No fields configured for Security.
Projects
- Status
Activity
chore: agent-claim #268 nonce=11f2379d18b0adf335cfe68e88ba968d
devantler commentedon Oct 5, 2026
Acceptance is verified in merged PR #281, source commit 4f897fa. Release tag v2.4.2 points to that source. Application and chart publication succeeded, including the independent published-image signature, source-label, offline-command and portable UI-host smoke checks.
The exact PR head passed all hosted checks, including the complete Kubernetes lifecycle and native source-query acceptance jobs, with no unresolved review finding. Meaningful local regressions also cover denial before foreign reads, readiness withdrawal/recovery and strict configuration parsing with healthy controls.
The final Platform upgrade, including the remaining four UI corrections, is tracked separately in Platform #4499.