bug(review): bound STATUS loses committed-range selector after Pi restart, and baseRef input is unreachable from direct tool calls (4.3.0) #2379

Before submitting

• I searched open and closed issues and did not find a report of this problem.
• I reviewed this report and removed credentials, tokens, private paths, hostnames, and other sensitive data.

Problem

After a Pi restart, gentle_review status with the exact retained lineageId no longer resolves an open committed-range lineage. The facade keeps the lineage's committed-range selector only in memory (CandidateViewRegistry.projections), so after the restart STATUS falls back to the workspace current-changes projection: applicability: "unrelated", next_transition: collect / empty_candidate_base_ref_required, and repair counts lineages: 0. The native authority is intact (review-state.json: state: correction_required, selector base-diff with a full base_ref, 4 admitted role results).

The only workaround, passing {"baseRef":"<FULL_SHA>","committedOnly":true} to STATUS, is unreachable: the facade requires input to be a serialized string for every operation except START/ASSESS, and the tool-call layer always JSON-parses string values that look like JSON into objects. Same root class as #2375 (answer-consent) and #1573 (fixed for START/ASSESS only).

Steps to reproduce

1. RDD on; START a committed-range lineage (baseRef + committedOnly: true) and drive it to correction_required with a targeted-validator slot pending.
2. Restart Pi (e.g. to set GENTLE_PI_REVIEW_RELAY_PI_TIMEOUT_MS after a relay timeout).
3. gentle_review status with lineageId (with or without workspaceRoot).
4. gentle_review status with input {"baseRef":"<FULL_SHA>","committedOnly":true}.

Expected and actual behavior

Expected: STATUS reoffers the pending validator slot for the lineage, either because the facade restores the committed selector from native state or because STATUS accepts input as an object like START/ASSESS do.

Actual:

• Step 3: applicability: "unrelated", workspace projection, empty_candidate_base_ref_required, no collect bindings.
• Step 4, object form or with leading whitespace: Review controller input must be a string.
• Step 4, escaped string: schema validation fails (must match pattern "^\s*\{").
• inspect only offers a fresh whole-range START, which had already hit lens_context_budget_exceeded.

The lineage is stranded with no supported facade route. Nothing was mutated.

gentle-pi version

4.3.0 (gentle-ai 4.2.0, contract gentle-ai.review-integration/v2)

Pi version

Pi coding agent 1.3.0

Operating system

Windows (amd64)