CLI Update Enforcement Grill Log

Branch: Version Pins

Q1 Question: What state should the scaffolded repo remember?

Accepted answer:

• .devpunks must contain cliVersion and baselineVersion pins.
• cliVersion changes when the project uses a dp CLI version as the local command authority.
• baselineVersion changes whenever scaffold-managed content is written through scaffold/update flows.

Q2 Question: Where should the pins live?

Accepted answer:

• Store pins in .devpunks/settings.json, alongside provider/tool state.
• Avoid putting the mutable local CLI pin inside scaffold-manifest.json; that manifest is primarily managed scaffold output evidence.

Branch: Drift Command

Q3 Question: What command should own version drift checks?

Accepted answer:

• Add dp check.
• dp check is read-only by default.
• It checks both CLI drift and baseline drift.
• It should become the command invoked by session-start hooks.

Branch: Session-Start Enforcement

Q4 Question: What should happen when drift is detected on session start?

Accepted answer:

• Warn before work starts.
• Summarize related changelog content so the user knows what the update contains.
• Prompt the user to update before continuing work.
• Preserve the existing successful clean-path behavior, currently equivalent to Harness scaffold check: OK.
• Exact hook wording and changelog extraction mechanics are implementation details for delivery, not open requirements.

Branch: Subagent-Owned Updates

Q5 Question: Who runs accepted remediation?

Accepted answer:

• If the user accepts the update prompt, the actual update flow must run in a subagent.
• The main thread should not perform write-capable update remediation itself.

Backlog Implications

• Add a CLI story for persistent .devpunks version pins and migration/backward compatibility.
• Add a CLI story for dp check drift detection and changelog summary output.
• Add a hook/guidance story to replace session-start dp update --check calls with dp check.
• Add a skill/docs story to update $dp-cli, command guidance, runbooks, and generated handoff language.