Skip to main content

Roadmap

Missing pieces​

  • A DRS-style release document (v1.0.8) with theme, highlights, and design boundaries
  • Project manifest release block (installer path, package_version, size_bytes, sha256)
  • Per-version verification records appended to a release checklist (build/test/install/uninstall evidence)
  • Release evidence bundle (release-evidence/v1.0.8/) with filehash.txt, build.log, test.log, install-check.txt
  • Explicit SHA-256 artifact hash recorded in manifest and release note
  • Signing status statement for the installer (code-signed / self-signed / unsigned)
  • Confirmation that docs/ is copied into publish output and included in the installer
  • Automated reproducible-build instructions or a build reproducibility guide

Next steps​

  1. Perform a full release verification: build the release installer, compute SHA-256, capture build/test/install logs
  2. Write a DRS-compliant release note for v1.0.8, placed in docs/ and the release-evidence bundle
  3. Update AptlantisConsole.manifest.toml with a release block: installer path, package_version (1.0.8.0), size_bytes, sha256, release.verified
  4. Append a per-version verification block to the release checklist, recording test counts and install/uninstall results
  5. Assemble release-evidence/v1.0.8/ with filehash.txt, build.log, test.log, install-check.txt — never modify after creation
  6. Document signing status, and either add code-signing to the build pipeline or record self-signed status explicitly

Potential improvements​

  • Generate an SBOM (CycloneDX/SPDX) into artifacts/sbom/ for supply-chain visibility
  • Automate tauri:build in a CI job producing reproducible artifacts and verification logs
  • Move long-lived UI/operational state from localStorage to DuckDB for versioning and migration support
  • Formalize a Data Migration Contract before introducing schema changes to persisted DuckDB/TOML data
  • Add a small build reproducibility guide with pinned tool versions to reduce environment drift

Creative enhancements (ideas on file, not committed)​

  • Operational Memory Graph: correlate screenshots, commands, terminal sessions, errors, and runbooks into a local graph for fast temporal queries
  • Embed CommandWizard fully: surface help-imported TOML schemas inline so command construction is a first-class AptConsole object with DuckDB history
  • Portable evidence export: a signed ZIP containing release-evidence, a DuckDB snapshot, and selected artifacts for offline handoff
  • Local LLM assistant integration (via Ollama) to auto-summarize captures into runbook steps or suggest remediation commands
  • A local-first plugin marketplace: load user-contributed command-schema packs, DuckDB views, and UI widgets as sidecar directories
  • A desired-state visualizer for winget, comparing snapshots and presenting drift with suggested reconciliation commands