Public Runtime Bindings surface cleanup

[zack-nova]

Parent

#136

What to build

Finish the release-facing Runtime Bindings product surface after the schema, renderer, commands, and install behavior land. Public docs and help should teach hyard vars, .harness/vars.yaml, schema 2, and strict {{ vars.<name> }} behavior while keeping plumbing terminology out of normal user paths.

Acceptance criteria

• Public CLI help teaches hyard vars as the Runtime Bindings management surface.
• Product documentation and examples use .harness/vars.yaml, Runtime Bindings, and Package Variables terminology consistently.
• Public documentation does not teach .orbit/vars.yaml, schema 1, scalar shorthand, $name Package Template References, unresolved placeholders, --strict-bindings, or public --allow-unresolved-bindings as supported product behavior.
• Any retained lower-level bindings command tree is documented, hidden, or framed only as plumbing where genuinely required.
• Release-surface validation is updated for hyard vars, schema 2, strict install behavior, and strict Package Template Reference syntax.
• mise run fix, mise run ci, and sh ./scripts/test_release_surface_hyard.sh pass after the public help/docs changes.

Blocked by

• Runtime Bindings schema v2 and canonical validation #137
• Runtime Bindings resolution, defaults, doctor, and explain #138
• Sensitive Package Variable policy and redaction #139
• Strict Package Template Reference rendering #140
• Strict non-interactive Package Installation #141
• Runtime Bindings init and interactive install onboarding #142

[zack-nova]

This was generated by AI during triage.

Triage Notes

• Dependency release closeout for Runtime Bindings schema v2 and canonical validation #137: PR Implement Runtime Bindings schema v2 #144 landed successfully at merge commit 760c38334b3de16830449d509c25a8258d90b168.
• This issue still lists Runtime Bindings resolution, defaults, doctor, and explain #138, Sensitive Package Variable policy and redaction #139, Strict Package Template Reference rendering #140, Strict non-interactive Package Installation #141, and Runtime Bindings init and interactive install onboarding #142 in ## Blocked by; those issues remain open.
• State update: leave state:blocked in place until the remaining blockers are resolved.

[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 schema v2 and canonical validation #137, Runtime Bindings resolution, defaults, doctor, and explain #138, Sensitive Package Variable policy and redaction #139, Strict Package Template Reference rendering #140, Strict non-interactive Package Installation #141, and Runtime Bindings init and interactive install onboarding #142.
• Sensitive Package Variable policy and redaction #139, Strict Package Template Reference rendering #140, Strict non-interactive Package Installation #141, and Runtime Bindings init and interactive install onboarding #142 remain open and unmerged, so blockers remain.
• State unchanged: keep state:blocked.

[zack-nova]

Triage

All listed blockers (#137, #138, #139, #140, #141, #142) are now merged, so this can move out of blocked state.

Initial scope read:

• Public help/docs should teach hyard vars, .harness/vars.yaml, schema 2, Runtime Bindings, Package Variables, and strict {{ vars.<name> }} syntax.
• Public docs should stop teaching legacy .orbit/vars.yaml, schema 1, scalar shorthand, $name references, unresolved placeholders, and hidden compatibility flags as product behavior.
• Release-surface validation needs to assert the public Runtime Bindings surface.

[zack-nova]

Dev Brief

Scope for this pass:

• Tighten public hyard help around hyard vars, Runtime Bindings, schema 2, and .harness/vars.yaml.
• Add docs onboarding for hyard vars init, explicit --defaults, sensitive value_from.env, and strict {{ vars.<name> }} references.
• Expand release-surface validation so Runtime Bindings public behavior is protected.
• Keep lower-level bindings material framed as plumbing/compatibility only where it remains in historical command trees.

Feedback loop: TDD with help/docs/release-surface assertions first, then docs/help changes, followed by mise run fix, mise run ci, and explicit release-surface validation.