harnessed-update

Topics in the source

• harnessed-update
• Overview
• Process
• Boundary
• How to invoke

One interactive entry point for deterministic self-update, harnessed-owned asset refresh and reviewed updates of already-installed third-party components. The CLI is the source of truth, not an agent's interpretation of installer logs. 1. Run harnessed update --all --dry-run --json for a read-only preview. Capture stdout, stderr and the exit code separately. Read exactly one JSON object from stdout even on nonzero exit; stderr contains diagnostics, not result data. Validate schemaVersion=1, operation=update, mode, host and runtime. Missing or malformed JSON, error or failed preview components mean STOP. A preview containing unsupported is still partial; show those limits. 2. Show the proposed changes and ask for explicit confirmation via {{ host.askuser }}. Cancellation, silence or unavailable confirmation means STOP without mutation. A delegated subagent without approval must return STATUS: NEEDSCLARIFICATION for the main session to ask the user. 3. Only after confirmation, run harnessed update --all --json exactly once. The CLI owns P1 self-update and verified absolute-path P2 continuation; do not launch continuation yourself or refresh assets from the replaced runtime. 4. Displa

This is an excerpt. Refer to the complete source and its current requirements.