Skip to content

Prioritized delivery backlog and dependencies #58

Open

Description

@Anheledir

Updated: 2026-10-26. Canonical issue index for the agreed remaining work. Individual issues contain scope, acceptance and dependencies; existing focused acceptance tasks were retained rather than duplicated.

Recommended execution order

  1. Measure and reduce CLI startup latency and distribution size #25 startup work is merged in Reduce startup overhead and benchmark native single-file launches #59; actual Windows Home measurement remains. Evaluate Native AOT and trimming for smaller, faster standalone releases #26 has a promising partial-trim + ReadyToRun candidate; Replace reflection-based JSON with typed contracts and source generation #60 typed/source-generated JSON is completed in Use generated JSON contracts for storage, IPC, bridge and CLI output #63. Make CLI command registration compatible with trimming and Native AOT #61 CLI metadata/AOT compatibility is the next release-enablement task.
  2. Add previewable repair of managed integration executable paths #30: repair existing managed hooks safely; Guide first-run installation, output setup and first state delivery #31: finish first-run setup; Build a responsive terminal frame and live host/session overview #32/Terminal accessibility and scripting acceptance #7: responsive frame and real terminal acceptance.
  3. Publish a documented SidePulse .NET library for embedding #27 → Design the embeddable client API and migrate CLI application services #28 → Package the library with API documentation and runnable consumer samples #29: reusable public API, CLI adoption, documented preview NuGet package and consumer samples. Use performance findings; AOT is not a hard prerequisite.
  4. Complete host/output robustness, migration, current-provider acceptance, release/update hardening and signing decisions. Fix Prevent duplicate release drafts for an already published version #57 before preparing the next release version.
  5. Schedule P3 only after core work, with explicit feasibility decisions before promising support.

P1 — next delivery

P2 — follow-up implementation and acceptance

P3 — deferred research and expansion

Existing acceptance and coordination issues

Current baseline

Beta.1 and beta.2 are publicly published; the maintainer reports beta.2 passed a local retest. #24 adds persistent preferences/Home/form recovery after beta.2. Do not recreate completed #19/#23 work. Native CI, fixture acceptance and physical/provider/user evidence remain distinguishable. P3 is a backlog, not a claim that optional features are implemented. No releases, package feeds or messages to third parties are published by this triage.

Activity

  1. added
    documentationImprovements or additions to documentation
    P2Follow-up: acceptance, robustness and integrations
    on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Follow-up: acceptance, robustness and integrationsdocumentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions