v1.3.31 - Safe reconstruction changes

Request-driven changes to existing reconstructions now have focused guidance for reconciling current intent and custom code with retained compatibility, tracing shared dependencies, selecting acceptance/regression checks, and choosing proportional data recovery. New reconstruction requirements stay distinct from reference-version and environment changes; planning remains separate from implementation authority.

The bounded Pocket Ledger example freezes the original baseline and literal outcomes before adding a completion action. It exercises retained listing/import/export, rejected edits, injected save failure/retry, reopen and previous-code readback, with six targeted faulty variants. Manual contextual judgments and runtime observations remain separate; this does not certify arbitrary model comprehension or global compatibility.

Validation includes 535 source and extracted-package tests, eight client/integration install cases and eight exact-ZIP upgrades, manifest/link/privacy checks and genuine skill validation. The CI matrix retains three existing Linux platform skips. Historical evidence and installer/updater/integration safeguards are preserved. Same-agent source-exposed review; no additional runtime dependency, provider or service.