qargi 0.2.13

Changed

• Member tasks can reuse lead-supplied passing baseline evidence for the exact BASE_SHA when relevant input and check definitions match, recording its reference, SHA and provenance in deviations[] rather than claiming a run or gates pass. They run focused checks and applicable gates for each change, then DONE on final HEAD after all outcomes and again after later changes; profile gates and the lead's whole-suite checkpoint remain in force.
• qargi feature park and automatic parking follow allow nonconflicting untracked runtime files while refusing tracked changes, parking-branch commits absent from develop, and collisions with untracked or ignored files. A failed automatic follow leaves the parking branch behind without undoing a successful integration.
• Installation examples distinguish user and project choices, and the memory tiers example aligns its columns.
• Documentation examples and explanatory tables fit narrower GitHub views more readily.
• Ordinary clean retains the read-only product refusal independently of refs-only observation: unexpected patches or a bundle preserve the run even with zero extra clone commits. An unchanged internal refs verdict grants neither verification nor artifact acceptance; explicit discard deliberately recovers it and reports actual refs.
• Inspection failures now show sanitized reasons in run, verify, review check and clean. The 0.2.13 limits stay fixed: 512 MiB copied metadata (the whole object store included), 1 MiB config, 100,000 traversal/read steps, 64 directory levels and 60 seconds for copy traversal and each Git subprocess. Ordinary prepared clones are supported only within those bounds. Ordinary clean preserves every artifact when worktree state is unknown, including when commit inspection succeeds; explicit discard remains deliberate recovery after preserving wanted work.
• Inspection disables replacement objects, preserves the difference between valueless (true) and explicit empty (false) Git booleans, and uses a minimal format-0 config for SHA-1 while keeping explicit SHA-256 format support. Regressions include replacement refs and a same-length, restored-mtime racy-index case with a negative control.
• When the run directory still exists, classless registered legacy discard reports the authoritative refs verdict, including unexplained real ref changes. Its internal refs-only observation neither verifies the run nor saves accepted output or grants class permissions; ordinary unknown-class refusal remains.
• Unexpected runner failures retain nonsecret start/process and home metadata, cleanup status and refreshed-file residue for list and verify. Retry checks the original group for every dispatch outcome and refuses known or unknown survivors until quiescence can be established, without signalling a potentially recycled PID. A partial home setup whose cleanup also fails keeps an explicit cleanup note alongside the planned link names.
• feature finish validates project identity/answers and strictly parses and enumerates the same registry snapshot. Missing/malformed answers, dangling/unreadable/malformed registries and reader failures refuse; empty exit 1 and traceback output are distinguished from valid open-run rows. General diagnostic readers remain tolerant. This removes the double-read path but provides no coordination of new preparation through the eventual merge.
• Local runs stop remaining members of the original process group before removing authentication links and inspecting output, including on normal exit and unexpected runner errors; surviving members fail an otherwise successful run. Unexpected errors retain the original exception even if cleanup also fails, and an unreadable survivor count stays unknown.
• The lead verbs and guard MCP policy validate the decoded JSON class against the exact supported registry strings before shell decoding and preserve malformed runs for investigation. Explicit clean --discard remains a recovery route for known registered legacy runs without a class; it intentionally drops evidence and cannot discard unregistered runs. A member's review check requires its marker to resolve to the inspected run, then checks structure without lead registry authority, verification, scrub marks or cache. Lead review checks validate class before renewing the lease. Pre-existing guard shell/write tightening still consults the member class file; those paths and their heuristics are unchanged.
• Clone inspection reads a bounded private metadata copy in trusted lead state with a minimal configuration and an absolute Git resolved once from the lead's controlled PATH, so even a newly inserted filter cannot execute during inspection. The copy preserves index timestamps for same-length write detection and supports SHA-1 and SHA-256. Unsupported metadata layouts and inspection failures stay unknown; ordinary clean preserves unknown commit state. Copies may combine concurrent states and do not contain escaped sessions.
• Expected setup refusals retain planned sign-in link names if partial cleanup fails, so list and verify can locate residue. Unreadable process-group probes no longer prevent TERM-to-KILL escalation; an unreadable final count remains unknown. Cleanup marks the run cleaned without granting verification, including when no prior verify was run.
• Feature finish requires repository identity for any run path that exists or cannot be inspected. Structurally valid records for confirmed-absent run paths do not block finish solely for missing identity; the records are not deleted, rewritten or granted authority.