Skip to content

1.1.0 guided progression: contract, companion state and desktop inputs - #297

Draft
Laymer wants to merge 10 commits into
mainfrom
feat/v1.1-guided-progression
Draft

Laymer wants to merge 10 commits into
mainfrom
feat/v1.1-guided-progression

Conversation

@Laymer

@Laymer Laymer commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

Navzeroth 1.1.0 requires four usable guidance workflows and exact launch-build compatibility. This draft records the approved release contract and adds the shared progression foundation: bounded/versioned companion exchanges, exact predecessor binding, immutable SQLite storage with separate manual/imported origins, guarded application/native commands, generated API contracts, and an explicit Imports panel for companion exports and manual money/talent-point observations. Blank values remain unknown and manual entries never change game state. The website asset validator and inert reviewed-evidence importer explicitly admit 1.1.0; evidence imports select only the requested version subtree. The artifact policy records the approved unsigned1.1.0 exception.

Validation: core/ingest/storage and focused application/recovery tests passed (see task handoffs for exact scopes); 571 desktop unit tests passed with the per-file 90% line gate; desktop typecheck/lint/build, contract fixtures, and one Chromium command-mock input/import/reload journey passed. Independent read-only reviews covered the shared state, storage/recovery, application boundary and input UI. The evidence transport suite passed20 tests (one native Windows junction check skipped on Linux), with91.7% local trace line coverage.22 Linux PowerShell policy checks passed. Hosted checks on this head remain authoritative; no native/live gameplay acceptance is inferred from mocks.

Still required before release: evidenced interface for installed wowf 1.60.1.70862, regenerated/reviewed content, typed gameplay facts and coverage, full manual/addon capture, saved plans and all four guidance workflows, remaining version-aware release tooling, fresh signed bundles, exact protected-main/source-parity/stability and Windows installer/draft acceptance. This remains a draft; no merge, tag or publication readiness is claimed.

Current records: docs/decisions/0011-v110-guided-progression.md, TODO.md, and docs/handoffs/2026-11-10-v110-progression-inputs.md.

Hosted attempt on d823b0d: Windows packaging42836215251/1 stopped at signed bundle production mismatch against retained1.0.0 closure; no installer/native acceptance ran. This refusal remains enforced until fresh reviewed1.1.0 closure after feature/content freeze. See docs/handoffs/2026-11-10-v110-evidence-version.md.

@Laymer Laymer changed the title V110: establish release contract and progression state foundations V110: add progression exchange and persistent companion state Nov 10, 2026
@Laymer Laymer changed the title V110: add progression exchange and persistent companion state 1.1.0 guided progression: contract, companion state and desktop inputs Nov 10, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant