LoopSkill v3.3.1

LoopSkill v3.3.1 fixes two release-blocking schema-v3 paths:\n\n- target-owned validation evidence can now be atomically archived by runtime_codec STAGE_REPORT and recovered on the original outbox without a second product dispatch or repair attempt;\n- max_repair_attempts_per_goal=0 now initializes legally while the first completed failure still deterministically exhausts the strategy and later dispatches remain fail-closed.\n\nRelease authority and evidence:\n\n- protected main exact commit: dc4f242\n- exact tree: e578f7a3d4e5002af693e17b607c1fdcf71c79aa\n- independent Reviewer: P0/P1/P2 = 0/0/0\n- full unittest: 655 PASS\n- branch coverage: 80.06% (minimum 80%)\n- generator fuzz: 5000 PASS\n- state fuzz: 5000 PASS\n- Skill, SPEC, schema inventory, installer, whitespace, risky-artifact, and secret/auth gates: PASS\n- exact-main same-SHA install: v3.3.1, source/install drift empty, configuration readback true\n- real Codex App patch canary: PASS; schema-v3 zero-repair INITIALIZE, one real send, cross-task VERIFY, complete diff, two zero-side-effect evidence rejections, one legal target-owned stage, and REPORT_RECOVERY on the original outbox all completed. Canonical reached state version 4; outbox COMPLETED; route RECOVERED; dispatch count remained 1 and repair attempts remained 0.\n\nEvidence boundary:\n\n- the earlier exact-main patch canary remains immutable FAIL because its harness baseline ignored validation-source.json; the runtime rejected that input with no state corruption. It is not rewritten as PASS.\n- the corrected fresh fixture receipt is SHA-256 75d2448a11b707f09eb5c1f0a8dc1b12141a91044414c8812a6c209cb67f7751.\n- GitHub Compatibility CI is a mirror and was not used as this release authority under the explicit user-approved boundary. No CI conclusion is claimed here.