v4.15.3 — portable recovery writes and release completion
v4.15.3 carries the recovery, Fusebase CLI coexistence and maintainer-process work prepared in the
unpublished v4.15.0, v4.15.1 and v4.15.2 tags. The v4.15.2 tagged gate passed Linux and verified the
full skill and agent mirror corpus on Windows before legacy recovery exposed the last caller using
an absolute MSYS source path; publication remained skipped.
Delivered behavior
| Area | Behavior |
|---|---|
| Recovery and CLI coexistence | Recovery preserves consumer and CLI-owned bytes, restores authorized Flow surfaces, retains originals for owned repairs, revalidates before apply, reports partial/refused states truthfully and converges without rewriting current targets. |
| Portable recovery writes | Skill, agent, health-skill and command callers send repository-relative canonical sources. Skill and agent callers also send the exact authorized relative manifest for their surface. MSYS short paths and native Python long paths identify the same root without weakening source containment, manifest authorization or symlink rejection. |
| Phase reporting | Unexpected N/A, nonzero exits, timeouts, missing phases and zero-result phases remain failures. Only the declared off-MSYS signal-reap N/A is accepted. |
| Release verification | The tagged workflow runs the explicit 29-phase essential profile, runner-trust checks and package integrity on Linux and Windows/MSYS. Both legs and the aggregate gate must pass before publication. Full and focused diagnostics remain callable. |
Upgrade guidance
For a routine Fusebase CLI refresh, use:
fusebase update --skip-skillsAfter a full fusebase update, restore the Flow overlay and previously authorized wiring with:
bash hooks/local/post-fusebase-update.shAutomatic Git-hook restoration still requires prior Flow ownership proof. Use --wire-hooks only
when explicitly activating Flow hook wiring.
Evidence and limits
The v4.15.2 tagged run 34176386683 is failure evidence: Linux passed, Windows reached 633/634
essential predicates, and publication was skipped. Its full-corpus skill and agent write, no-op and
one-source-repair predicates passed. T71 then audited all four production writer callers and changed
only the remaining absolute health-skill source. The selected Windows legacy fixture passed migration,
preserved-value, second-run no-op and ambiguous-input zero-write behavior through an 8.3 temp path.
The v4.15.3 tagged two-platform workflow remains the only publication authority.
Validator receipt reuse remains disabled, so validators execute normally. Static context reduction,
fixture consolidation and no-op observations do not establish universal speed, host-token or
lint/typecheck savings. Ordinary-consumer timing, five-provider delivered-context telemetry,
real-symlink cases and Windows authority isolation/successful signing remain unverified.