# Development status — Recovery Horizon

Current published stable: **1.8.9**, September 16, 2026. The complete supplied
roadmap was reconciled on October 3, 2026. Existing work IDs remain unchanged;
the BSC aliases in the supplied document have an explicit crosswalk.

## Current release and preserved work

1.9.0 owns disk capture/validation, bootable media, disk restore and complete
post-restore evidence. Architecture approval and the disk/boot implementation
are still pending. The draft typed route contract is the current UI design work.

The implemented resource CLI has moved to **release/1.9.5**. Help, legacy
handbook and completion belong to **release/1.9.1**, adapted to the command tree
present there. Later release branches are scaffolds and do not establish product
readiness. Independent project-removal and text watcher safety fixes remain in
the 1.9.0 work. All prior work is retained in archive/1.9-before-roadmap-20261003.

See [complete release plan](Release-Plan.md),
[CLI development](CLI-Development.md),
[family contract](https://github.com/ATAC-Helicopter/VaultSync/blob/work/1.9-roadmap-realignment/docs/RELEASE_FAMILY_1.9.md),
and [Project #7](https://github.com/users/ATAC-Helicopter/projects/7).
Protected release integration remains PR-based; branch creation does not mean
that integration, native qualification or publication has completed.

## Remaining gates

Approve VS-1910/1917/1918/1919 before destructive disk implementation. Qualify
Capture → Validate → Boot → Restore → Validate on the declared matrix.
Portable, offsite, unified recovery, assurance and BSC follow in their own
releases. BSC gates cannot block earlier releases. No new individual patch dates
were invented; the existing family horizon remains planning context.

## Consolidated release PRs and qualification

There is one open draft PR per release: 1.9.0 #736, 1.9.1 #746,
1.9.2 #752, 1.9.3 #753, 1.9.4 #754, 1.9.5 #747, 1.9.6 #755,
1.9.7 #756 and 1.9.8 #757. Duplicate preparation/fix PRs are closed as
superseded; source branches and commits are preserved. All release PRs remain
draft and none is enabled for automatic merge.

Dependabot #661 (test SDK) and #720 (CodeQL) were reviewed and merged into Dev.
BUG-19010/#749 fixes incomplete rendering-family updates; BUG-19011/#750 ports
CLI overrides with the Spectre API upgrade. Those fixes are assembled in 1.9.0
and propagated to the implemented 1.9.1/1.9.5 CLI variants. Unused Inter font
packaging is removed; remaining library consumers and replacement candidates
are documented in the dependency inventory.

Full local suites after propagation: 1.9.0 937 .NET/107 Python; 1.9.1 942/116;
1.9.5 1056/116, warning-free full solution builds. BUG-19008 fixes captured console
disposal; BUG-19009 schedules mandatory workflows for embedded docs changes.
Current-head remote CI must be rechecked after release regrouping. Sonar previously
failed before analysis while looking up new PR keys; it is not claimed green.

[Complete daily work ledger](https://github.com/ATAC-Helicopter/VaultSync/blob/work/1.9-roadmap-realignment/docs/release-evidence/1.9-work-2026-10-03.md)
and [dependency audit](https://github.com/ATAC-Helicopter/VaultSync/blob/work/1.9-roadmap-realignment/docs/release-evidence/1.9-dependencies-2026-10-03.md)
record actual work, preserved history and remaining release gates.

## Active 1.9.0 workspace

The main working copy stays on `work/1.9-roadmap-realignment`, source of sole
[1.9.0 PR #736](https://github.com/ATAC-Helicopter/VaultSync/pull/736) into Dev.
All work intended to ship with 1.9.0 is added there. AGENTS.md, CONTRIBUTING.md
and the release contract record this context. The protected release/1.9.0 ref
retains older history and must not be mistaken for the assembled working tree.
Later-release implementation stays in its owning preparation branch and PR.

## October 4 protocol and architecture progress

All 44 historical release sections and own development notes now follow
[Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/) with standard
categories, ISO dates, version links and a maximum of 22 words per entry.
Original details and unshipped inherited development records remain archived.
Contract checks and 113 Python tests pass in all nine preparation copies;
1.9.0 additionally passes the warning-free Release build and 937 .NET tests
through shared Rider checks. Earlier suite counts above are historical.

VS-1917 image-format and VS-1919 identity/evidence contracts have review drafts;
serialization, fixtures, engine/support decisions and joint approval remain
open. Disk capture, independent boot and disk restore are unimplemented.
BUG-19012/#751 records the installed Linux font-manager startup block. Relaunch
passes initialization, but desktop visibility and durable remediation remain
unqualified. No release has been merged or published.

Six older protected-head drafts were superseded by preparation drafts retaining
all their commits. The protected refs were not rewritten. For current heads,
PRs, qualification limits and archived evidence, use the
[canonical family map](https://github.com/ATAC-Helicopter/VaultSync/blob/work/1.9-roadmap-realignment/docs/RELEASE_FAMILY_1.9.md)
and [October 4 ledger](https://github.com/ATAC-Helicopter/VaultSync/blob/work/1.9-roadmap-realignment/docs/release-evidence/1.9-work-2026-10-04.md).

## Imaging engine/support proposal — VS-1918

[ADR 001](https://github.com/ATAC-Helicopter/VaultSync/blob/work/1.9-roadmap-realignment/docs/adr/001-imaging-engine-1.9.md)
compares the engine options and proposes an isolated internal raw/offline worker.
The [qualification plan](https://github.com/ATAC-Helicopter/VaultSync/blob/work/1.9-roadmap-realignment/release/disk-support-1.9.0.json)
has four candidate GPT/UEFI ext4/NTFS sector profiles and zero qualified profiles.
Engine selection, initial platform scope and joint architecture approval remain
open. No imaging engine, elevation, raw-device operation or boot medium was added.

The read-only plan checker enforces retained approval and a complete measured
capture/validate/boot/restore/validate loop with bound identities, required stage
checks, UTC chronology and artifact hashes. It does not authenticate a producer
or prove hardware execution. The stable support gate intentionally fails with
zero qualified cases. 122 Python tests and Rider Contracts pass locally at
47589a2a; current-head remote CI and physical recovery qualification are separate.
VS-1918/#575 is In progress with original dates and open acceptance.