Skip to main content

Roadmap

Missing pieces​

  • Release document is missing the SHA-256 hash for the MSIX artifact (RELEASE-v1.0.0.md lists packaging and signing but no SHA-256)
  • Project manifest lacks per-release installer SHA-256 and release.verified fields
  • Release note is missing the required Design Boundaries section and explicit theme name per the DRS template
  • Release note is missing a Built With section listing notable dependencies in the DRS-prescribed format
  • No evidence folder (release-evidence/v1.0.0/) with filehash.txt, build.log, test.log
  • Build/test/package commands need re-confirmation per the governance reconciliation notes

Next steps​

  1. Compute SHA-256 (and optionally BLAKE3) of dist\CommandWizard-1.0.0.0.msix and record it in RELEASE-v1.0.0.md and the manifest's release.installer.sha256
  2. Run a verified clean build, record build.log/test.log, populate manifest.release.verified, and append a per-version verification block to the release checklist
  3. Create a release-evidence/v1.0.0/ bundle with filehash.txt, build.log, test.log, install-check.txt, referenced from the manifest
  4. Add the DRS-required fields to the release note: explicit theme name, Design Boundaries (≥2 entries), Built With list, signing status statement
  5. Confirm and update the project lifecycle state (paused vs. active) with the maintainer, reconciling legacy manifest fields into the canonical manifest

Potential improvements​

  • Include an in-installer docs/ folder with the release note and trust/security notes, so documentation travels with the install
  • Add automated UI smoke tests or headless verification steps to the release checklist
  • Optional SBOM generation (CycloneDX/JSON) for any future public release
  • A small CLI mode for headless schema import or command generation, to integrate with other Aptlantis pipelines
  • Export/import and sync primitives for sharing schemas between Aptlantis tools (local git or DuckDB-backed index)

Creative enhancements (ideas on file, not committed)​

  • A "share schema bundle" feature exporting a verified schema + sample commands + metadata as a single signed archive for safe exchange between operators
  • Auto-generated shell-specific command snippets (bash, PowerShell, fish) and optional completion files from the schema
  • A local "schema catalog" service (DuckDB) to query and index installed schemas and favorites across Aptlantis tools
  • A contextual "task-to-command" assistant mapping natural-language tasks to templated command sequences using existing schema metadata
  • A reproducible packaging mode recording build input hashes and emitting a small provenance.json for later artifact verification