Roadmap and Risks

Roadmap And Risks

This page records current owner decision points and future hardening work after the runtime-boundary alignment merge.

Current State

flowchart LR
    Merged["Runtime-boundary implementation merged"]
    Source["Source contracts updated"]
    Docs["Repo docs and Wiki aligned"]
    Native["Native Windows validation still required"]
    Future["Owner-directed next work"]

    Merged --> Source
    Merged --> Docs
    Source --> Native
    Docs --> Future
    Native --> Future

Loading

Owner Decision Points

Area	Decision Needed	Priority
Native validation closeout	Run Debug/Release CMake, CTest, MSVC, PowerShell guardrails, and vcpkg validation on Windows; record the result under .forsetti/alignment.	P0
Remote build/test parity	Add a Windows-hosted build/test workflow after native local validation is stable.	P1
vcpkg baseline pinning	Decide whether to add builtin-baseline for reproducible dependency resolution.	P1
WinUI host shell integration	Decide how the sealed host template maps to a concrete WinUI 3 shell and view composition layer.	P2
Theme policy	Decide whether modules may ever own or influence ThemeMask.	P2
Module-originated framework events	Decide the public API shape for module-originated general events beyond module-to-module messages.	P2

Future Hardening Work

Area	Follow-Up
UI field shape	Validate duplicate toolbar IDs, unknown slots, duplicate view injection IDs, and overlay route consistency.
Platform integration testing	Add deterministic live WinHTTP success-path tests with a controlled local HTTP server.
Registry test cleanup	Provide optional cleanup tooling for old test registry roots.
Capability service mapping	Add new governed services to CapabilityScopedServiceProvider as APIs are introduced.
Script regression coverage	Expand Scripts/test-guardrail-scripts.ps1 when guardrail behavior grows.
Host shell bridge	Add concrete Windows UI binding only after the host shell architecture is approved.

Host Template Status

ForsettiHostTemplate is now an active static library target. It provides host bootstrap, controller, launch strategy, overlay router, state snapshots, and surface-state adaptation. It is not a concrete WinUI 3 application shell.

Current dependency flow:

flowchart TB
    Demo["samples/ForsettiDemo"]
    Host["ForsettiHostTemplate\nactive static library"]
    Platform["ForsettiPlatform"]
    Core["ForsettiCore"]

    Demo --> Host
    Host --> Platform
    Host --> Core
    Platform --> Core

Loading

Remote Workflow Restoration

Recommended path:

1. Keep the existing repository surface workflow.
2. Run the full local Windows/MSVC validation stack and record the result.
3. Add a Windows build/test workflow using the repository debug preset.
4. Cache or configure vcpkg consistently.
5. Run Scripts/verify-forsetti-guardrails.ps1.
6. Require the workflow after it is stable.
7. Update README, Wiki, and governance docs to mark remote parity restored.

Release Readiness Checklist

• Local guardrail wrapper passes on Windows/MSVC.
• Remote repository surface workflow passes.
• Remote build/test workflow exists and passes, once restored.
• Changelog entry is complete.
• README and Wiki reflect current targets.
• Public API changes are documented.
• Remaining owner decisions are either resolved or explicitly tracked.