Skip to content

v0.21 planning: native viewing, semantic output, /track and context polish #410

Closed

Description

@raiseCatError

v0.21 — terminal intelligence, native viewing and core workflow polish

Planning umbrella, not a claim of implementation. Baseline is the current verified dev after v0.20.0 release/maintenance; recheck exact SHA before implementation. One substantial v0.21 delivery with independently reviewable slices and honest release gates. Do not auto-create a v0.22 milestone or expand scope without maintainer review.

Product goal

Make the existing real-shell/PTY frontend more useful and reliable for viewing files/output, editing small text files, tracking finite commands, understanding output, managing context, and personalizing appearance. Keep the composer, shell input ownership, raw transcript and terminal-host interoperability authoritative.

Do not build a Bash/zsh education platform. #398 is a separately deferred, optional future contextual NMSh guided tour and is not a v0.21 dependency or public website feature.

Priority / linked scope

Required reliability/integration gates

Core v0.21 feature slices

Explicitly outside v0.21

Engineering plan

  1. Baseline audit: exact released/working branch SHA, AGENTS.md, CONTRIBUTING.md, PR/issue reconciliation, maintained T7 workspace, existing frontend/service architecture and tests. Do not recreate shipped Background tasks: supervised long-running commands, task bar above the composer, and conservative suggestions #382 supervisor, present markdown system or theme catalog.
  2. Specifications and tests first, small dependency ordered PR slices. Audit PTY escape/raw handling, renderer ownership, keyboard focus, persistence, security and resource limits.
  3. One primary Opus Extra High agent for coherent architecture and lower repeated context. No subagents by default; allow bounded Sonnet delegation only by later explicit cost/ownership justification.
  4. External T7 fail-closed for disposable worktrees, build/test outputs and caches; leave source worktrees and OS-managed locations intact. Don't run redundant full suites on each slice; focused tests until integration gate.
  5. Release gates: named regression tests, macOS/Linux/Node 22/26 CI, security/performance smoke, 8 GB Mac budget and human physical Ghostty/Terminal.app QA; explicitly list unsupported hosts. Exact tag/release only after authorization and acceptance. No claim that green CI equals physical validation.
  6. Docs/site: current versioned docs and release notes, no Learn promotion. The NMSh site is live at https://nmsh.raisecaterror.com/; keep Cloudflare production deployment manual-only with required protected-environment approval.

Definition of done: every accepted feature is integrated, user-reachable, documented and verified at the exact commit; remaining partial features have accurate issues and disclosure. After the first substantial slice, present an evidence-based option to expand v0.21 rather than manufacturing an automatic v0.22.

Activity

  1. raiseCatError commented on Oct 18, 2026

    @raiseCatError
    OwnerAuthor

    v0.21 candidate status: all planned slices are in stacked PRs, awaiting the maintainer's merge and physical QA. Nothing is tagged or released.

    Slice Issues PR
    Design and ledger #410 #411 → dev
    Reliability gates #403, #408, #388 #412
    /view #397, #402 #413
    /edit #402 #414
    Semantic Output (phase 1) #386 #415
    /track (reconciles draft #394) #393 #416
    Native modules, explain and timings #364, #365 #417
    Theme families; action controls where needed #401, #336 #418
    Checkpoint ledger #410 #419

    Each PR targets the one before it; merge in order. Verification on the stack head: verify:release 3,115 of 3,118 pass (2 skipped, 1 known flake outside v0.21's changes that passes alone), bench:smoke within every budget. Physical QA checklist: docs/testing/v021-physical-qa.md (not run yet). The slice issues stay open until their changes are on dev and their physical passes are recorded. Deferred work (#398, #339/#340, #337/#338, #330–#332, #333, #334, #335, #399, #304, #341, #296, #389, #356) is untouched.

  2. raiseCatError commented on Oct 18, 2026

    @raiseCatError
    OwnerAuthor

    v0.21 stabilization pass: the candidate is integration-ready but not release-ready. Nothing is merged, tagged or released. The agent's merge into dev was refused by its permission policy ("merge without review"), so integration is with the maintainer.

    New stacked PRs (after #420): #421 /track review → #422 flaky CI at the cause → #423 bugs → #424 ledger. Exact-head CI on e8411e1a is green in every job, including Fedora portability and both timing smokes.

    Fixed

    Investigated, not reproducible: #356 (62 runs on macOS and Linux). #403 and #408 re-verified.

    Remaining gates:

    1. Ordered merges with regular merge commits (docs/development/v021-ledger.md → "Ordered integration").
    2. dev CI.
    3. A local verify:release on dev at normal load. In-session runs were overloaded by other workloads on the machine; the failing files then passed 69/69 three times at normal load.
    4. Physical QA in Ghostty and Terminal.app, mandatory and not run: docs/testing/v021-physical-qa.md.
  3. raiseCatError commented on Oct 18, 2026

    @raiseCatError
    OwnerAuthor

    Release audit, 2026-10-18. This supersedes the earlier "nothing is merged" note.

  4. raiseCatError commented on Oct 21, 2026

    @raiseCatError
    OwnerAuthor

    v0.22.0 is published (https://github.com/raiseCatError/notMyShell/releases/tag/v0.22.0). This planning issue's scope shipped there: the work is in master/dev (ef57ff43 and later) and the changelog lists it. The planning issue is closed; the individual issues under it stay open until their own acceptance and any physical validation is met, and the risks the maintainer accepted for the release (unrun physical checks, a queue-event attribution window, intermittent hosted macOS tests) are tracked in #473.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions