Strict non-interactive Package Installation

[zack-nova]

Parent

#136

What to build

Make public Package Installation fail closed in non-interactive and CI contexts when Runtime Bindings or Package Template References are incomplete or unsafe. This slice should remove unresolved placeholders from normal install output and make strictness the default product behavior.

Acceptance criteria

• Public hyard install flows fail before writing package-owned runtime output when required Package Variables are unresolved.
• Public hyard install flows fail before writing package-owned runtime output when strict Package Template Reference rendering reports unsupported namespace, unknown variable, unresolved variable, or malformed syntax.
• Non-interactive and CI failures include concrete recovery commands such as hyard vars init <package-source> --out .harness/vars.yaml and retrying install with --bindings .harness/vars.yaml.
• Unresolved runtime placeholders are not produced as normal public install output.
• Public install help and diagnostics no longer teach --strict-bindings as an advanced mode because strictness is default.
• Public install help and diagnostics do not teach public --allow-unresolved-bindings as normal product behavior.
• Existing readiness or install-record behavior is updated so unresolved placeholders are not treated as a supported public success path.

Blocked by

• Runtime Bindings resolution, defaults, doctor, and explain #138
• Sensitive Package Variable policy and redaction #139
• Strict Package Template Reference rendering #140

[zack-nova]

This was generated by AI during triage.

Triage Notes

• Dependency release closeout for Runtime Bindings resolution, defaults, doctor, and explain #138: PR Implement Runtime Bindings doctor and explain #145 landed successfully at merge commit 816afbf8d30ba71bc59fdf65e2d8686fa325dfa6.
• ## Blocked by lists Runtime Bindings resolution, defaults, doctor, and explain #138, Sensitive Package Variable policy and redaction #139, and Strict Package Template Reference rendering #140.
• Sensitive Package Variable policy and redaction #139 and Strict Package Template Reference rendering #140 remain open and unmerged, so blockers remain.
• State unchanged: keep state:blocked.

[zack-nova]

Triage Notes

• Blockers are resolved: Runtime Bindings resolution, defaults, doctor, and explain #138 is closed/merged, Sensitive Package Variable policy and redaction #139 is closed/merged, and Strict Package Template Reference rendering #140 is closed/merged via PR Implement strict Package Template References #147.
• Corrected stale Sensitive Package Variable policy and redaction #139 state label from state:to-merge to state:merged to match the closed merged fact.
• Scope is public install strictness: non-interactive/CI install must fail before writing runtime output when required bindings or strict template rendering are incomplete/unsafe.
• Public diagnostics/help should steer recovery through hyard vars init <package-source> --out .harness/vars.yaml and retry with --bindings .harness/vars.yaml, not through unresolved-placeholder success paths.

Next state: ready for implementation on issue-141-install-record-version.