Repository navigation
Locate unknown publisher fields at their safe schema-known container #288
Description
🤖 Generated by the Agentic Engineer
Problem
An unknown nested declaration field is rejected before publisher preflight collects source positions. The report points to the document root, losing the documented repair location even when the containing object is known.
Direction
Project private strict-decoder errors to schema-known container paths and source coordinates. Never include submitted unknown names or values in the public report.
Acceptance criteria
- Nested object and array unknown fields report their nearest safe container and original coordinates.
- Unknown names and values remain absent from both report formats.
- Ambiguous input and strict admission still fail closed.
Rough size: M.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Effort
None yet
Projects
- Status
Activity
chore: agent-claim #288 nonce=4ff87da55976e8983566cecdf38e2810
devantler commentedon Oct 5, 2026
Completed in merged #294.
Unknown-field diagnostics retain physical source coordinates and the safe schema-known container. Literal punctuation in submitted field names cannot forge provenance, and private submitted names and values remain absent from public reports.
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.