Reject linked desired-state documents in complete package validation #536

🤖 Generated by the Agentic Engineer

Problem

The complete package validator can report success while an onboarding desired-state document is linked outside the package and its contents were never fully validated. This lets unusable or non-contained onboarding configuration pass the gate used to ship the marketplace.

At current main 685d06b7398169cfd25245f6f55916538f4f41c5, a complete healthy package passes. Replacing its canonical desired-state file with a link to malformed configuration also passes and emits no desired-state validation result. The identical malformed configuration as a regular packaged file is rejected. The shipped regular document remains healthy.

The existing #379 delivery protects the digest writer. This is the separate package-validator consumer's discovery and containment boundary.

Proposed direction

Observe every desired-state document and resource-directory boundary before reporting package success. Refuse linked or nonregular documents and linked resource parents while retaining supported regular packaged resources.

Acceptance

• Preserve complete-package RED/GREEN controls for the canonical document, additional documents and linked resource parents, alongside a healthy regular package.
• Refuse unsupported filesystem boundaries before accepting or silently omitting their contents; incomplete discovery remains a failure.
• Keep the current marketplace, existing manifest and package-boundary regressions green.
• Deliver through native current-head CI, substantive review, protected merge and an exercised merged package gate.

Size: S. Part of #436.