Repository navigation
Enforce the provider publication policy consistently #293
Description
🤖 Generated by the Agentic Engineer
Requirement
The provider must apply its documented publication policy consistently to every supported configuration form.
Direction
Strengthen policy validation while preserving read-only observation and the existing credential boundary. Detailed security evidence remains in private operator notes.
Acceptance criteria
- Regression coverage exercises the supported configuration forms and rejects policy conflicts before publication.
- Valid dedicated reader publications continue to work.
- No credential values are read or exposed.
Rough size: M.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
No fields configured for Security.
Projects
- Status
Activity
chore: agent-claim #293 nonce=83a6ca5738a194fb3ed140976860b050
devantler commentedon Oct 5, 2026
Completed in merged #294.
The provider consistently applies the dedicated reader publication policy before admitting a product. Positive and negative metadata-only regressions and race checks pass. This evidence does not establish an external database's effective grants or live adoption.
All required CI passed at the reviewed signed source head. The combined release also passed targeted race regressions and the complete real-browser suite. The accepted implementation is on protected main.
Production rollout is tracked separately in devantler-tech/platform#4510; this closure does not assert that the new release is deployed or activate additional features.