Repository navigation
v0.22 design, ledger and natural-language proposal - #435
Merged
Merged
Conversation
Start v0.22 (#431) from dev a8b383c with a bounded scope: input reliability first (#426, then #356 under load), one workflow slice that reuses the editor bridge (#366: /view to the person's editor), two items that wait for the maintainer (#389 multiline history browsing, reproduced; natural-language command suggestions, #432), and every paused or deferred issue left as it is. v0.22 PRs target dev but stay draft until #430 has carried dev into release/v0.21.0: its head is dev, so anything merged earlier would ride into the release candidate. Nothing here touches the v0.21 release branch, its QA evidence, master or publishing. The natural-language proposal keeps one Ask: an optional, off-by-default suggestion outcome after the deterministic resolver, entered through an NMSh surface so it is never shell syntax, labelled by NMSh's own classifier, and run only by the person's Enter in the composer. It lists the decisions it needs, starting with whether remote model APIs belong outside the core at all. Refs #431 Refs #432
This was referenced Oct 18, 2026
7 tasks
This was referenced Oct 18, 2026
Open
…source findings The candidate (all nine PRs in dependency order) is green in CI on 567cf53 after two #437 follow-ups it surfaced. Records #442 and #443, the stacked #437, the conflict rule, the scratch combined /view editor test, what was recovered after the 2026-10-19 kernel panic, and the findings for the planned test-resource pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Starts v0.22 (#431) with a durable design and ledger, mirroring how v0.21 was run (#410,
v021-ledger.md).docs/design/v022-daily-use.md— goal, baseline and the v0.21 boundary (v0.22 PRs stay draft until v0.21 ships; nothing touchesrelease/v0.21.0, its QA evidence,masteror publishing), scope tiers, and per-slice behavior, boundaries, tests, performance and physical QA:/view→ your editor (draft /view: o opens the file shown in your own editor, at the line on screen (#366) #434).docs/design/v022-natural-language-commands.md— the design, now with the decisions and the first slice's scope (Ask: optional command suggestions from the local model, Copy/Insert only (#432) #440): one optional, off-by-default suggestion outcome inside the existing Ask, entered through an NMSh surface (never shell syntax), labelled by NMSh's own classifier, run only by the person's Enter; minimal context by default; providers local first, bring-your-own-key remote only if approved; cost and token estimates; the five decisions, answered.docs/development/v022-ledger.md— baseline SHAs, worktree and scratch locations, every slice with its PR (Input ownership: keys wait for the look, however long a loaded machine makes it (#426) #433–Composer history: History n/N on a free composer rule while browsing (#389) #441), decisions (why Input ownership: keys wait for the look, however long a loaded machine makes it (#426) #433 holds keys until the owner is known and a timeout never routes them, the two Flaky under parallel load: a command typed right after Ctrl+C on a waiting read can fail to run #436 mechanisms, D2's conservative label, Setup coverage), a verification table per PR, environment caveats, open risks.docs/testing/v022-physical-qa.md— the physical checklist: input ownership with the held-input states,/view→ editor, type-ahead after Ctrl+C and slow prompt hooks, history browsing andHistory n/N, terminal editor choice, Ask command suggestions. Nothing has had a physical pass yet.No code, no ROADMAP change (its status lines belong to the v0.21 release; they move at reconciliation).
Refs #431
Refs #432