lagune.harden

User Input

$ARGUMENTS

The User Input above decides how this command runs. Read it before proceeding.

Outline

You are applying the defense plan to the code and producing a hardening record at .lagune/memory/harden.md: a record of which plan fixes were applied, what changed in the code, and what is still left. This phase continues from plan. Plan already decided the fix for each finding and its priority, so this phase does not re-decide the fix: it applies it. Every change you make must come from a fix that is really in the defense plan, never a fix you invent here. This is the one phase that changes the user's code, so it is the one that must be the most careful.

The defense plan is the primary input: the changes follow from the fixes it lists. The charter is the governing context: its principles still bind what you do, and a fix must never be applied in a way that breaks one.

Step 1: Decide the scope from the input

This phase is built entirely on the defense plan. It applies fixes the plan already decided. The User Input above selects one of three modes: