Skip to main content

Roadmap

Missing pieces​

  • Project manifest version (1.0.0) doesn't match extension/manifest.json version (0.1.0) — needs alignment
  • No release.* fields present in the manifest (release.version, installer/packaging, release.verified) as expected by DRS reconciliation
  • Build, test, artifact packaging, and release verification were not executed or recorded
  • No packaged extension artifact (zip/CRX) or artifact hash recorded as release evidence
  • No release note / per-version human release document
  • No release-evidence folder (build.log, test.log, filehash.txt)
  • Signing / distribution posture (CRX signing or guidance) is not documented
  • The "docs copied into publish output" rule isn't recorded or implemented

Next steps​

  1. Align the project manifest version with extension/manifest.json's version, or document the rationale for divergence
  2. Perform an unpacked-install smoke test: install locally, exercise capture/export actions, record install/launch/uninstall results
  3. Create a minimal release note for the current version — theme, highlights, explicit design boundaries
  4. Produce a packaged extension artifact (zip or CRX), compute SHA-256, and record artifact filename + hash in manifest.release
  5. Append a per-version verification block to a release checklist (build result, test count, install result, data-safety checks)
  6. Add a small release-evidence folder with build.log, test.log, install-check.txt, filehash.txt
  7. Document signing/distribution guidance (self-signed CRX vs. local unpacked installs)
  8. Ensure docs/ (release note, trust note) are copied into the packaged artifact, or document an external canonical location

Potential improvements​

  • An automated packaging script producing a reproducible zipped extension with computed hashes
  • Lightweight automated smoke tests for key capture flows (article capture, screenshot, PDF export)
  • Recorded dependency provenance for vendored third-party libraries, and an SBOM for transparency
  • Embed release documentation (release note, trust statement) inside the publish output, keeping a canonical copy in the manifest
  • Configurable base download folder and a deduplication strategy for larger archival batches
  • An operator-facing CLI or headless mode (Puppeteer) for batch captures driven from URL lists

Creative enhancements (ideas on file, not committed)​

  • An "archive bundle" format packaging captured files + manifest + provenance.json for easy ingestion by Aptlantis dataset systems
  • A DuckDB-backed local index of captures with full-text search and deduplication for fast local queries
  • Browser-to-desktop handoff: index captured artifacts and push them to a desktop Aptlantis agent over localhost for downstream pipelines
  • Per-capture cryptographic provenance — signing a small provenance.json so downstream tools can verify origin and capture parameters
  • A small HTTP receiver in a desktop Aptlantis helper, accepting captures from the extension for headless archival and larger-scale batching