@dolusoft/command-console-core 0.0.0-stage → 1.0.1

package/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Dolusoft
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,203 @@
-# Temporary Holding Version
+# @dolusoft/command-console-core
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The engine of [Command Console](https://github.com/dolusoft/command-console): a headless console that ends lines,
+runs commands, keeps the scrollback, recalls and completes lines, and redacts sensitive lines. No framework, no DOM, no
+timer; it depends on `@dolusoft/command-protocol` only. The Vue package `@dolusoft/command-console` is built on it;
+use the core directly for another framework or a test.
+
+```sh
+pnpm add @dolusoft/command-console-core
+```
+
+The repository README describes the behavior a user sees (commands, returns and effects, completion, recall, keys,
+sensitive lines). This page describes the engine.
+
+## Creating a console
+
+```ts
+import {
+  completionFeature,
+  consoleFeatures,
+  contextFeature,
+  createConsole,
+  recallFeature
+} from '@dolusoft/command-console-core'
+
+const console = createConsole({
+  features: consoleFeatures({
+    recallFeature,
+    completionFeature,
+    contextFeature
+  }),
+  prompt: 'app>',
+  commands: [
+    { name: 'echo', run: request => request.rest },
+    // From argument 1 on the line is secret: it is never kept or handed out.
+    {
+      name: 'set',
+      sensitive: { fromArg: 1 },
+      run: async (request, run) => save(request.args, run.signal)
+    }
+  ],
+  onError: (error, info) => report(error, info)
+})
+
+const unsubscribe = console.subscribe(state => render(state))
+console.setInput('echo hello')
+await console.submit() // or: await console.run('echo hello')
+```
+
+The core features (`console`, `entries`, `input`, `dispatch`) are always present. `recallFeature`, `completionFeature`
+and `contextFeature` are opt-in, so a console that does not use them does not ship them. `consoleFeatures()` keeps the
+object's type: the instance type is computed from the features given, and a console created without `features` has
+no optional method, in its type and at run time. The feature set is fixed for the life of the console.
+
+## Options
+
+| Option                                                 | Meaning                                                                                                    |
+| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------- |
+| `features`                                             | the optional features, keyed `recallFeature` / `completionFeature` / `contextFeature`                      |
+| `commands`                                             | the `CommandDefinition`s; validated at creation and on every `setOptions` (a violation throws)             |
+| `prompt`                                               | the root prompt; default `'>'`                                                                             |
+| `initialState`                                         | the first `entries`, `recall`, `context`; every other slice starts empty                                   |
+| `state`                                                | a slice given here is controlled (below); it wins over `initialState`                                      |
+| `onEntriesChange`, `onRecallChange`, `onContextChange` | the reports of a controlled slice: one updater per action                                                  |
+| `createId`                                             | makes entry and run ids; default a per-console counter (`c1`, `c2`, …) that skips ids already in `entries` |
+| `maxEntries`                                           | drops the oldest entries beyond this, in the same action; default unbounded                                |
+| `beforeRun(info, signal)`                              | asked before a command runs; `undefined` goes on, `false` stops silently, a response ends the run with it  |
+| `onError(error, info)`                                 | a command threw or rejected (`info` is its `RunInfo`), or a callback threw (`info` is `null`)              |
+| `formatError(error, info)`                             | turns a command's error into its `CommandResponse`; default a `command-failed` entry                       |
+| `onClose()`                                            | the `close` effect                                                                                         |
+| `isSensitive(line)`                                    | marks more lines sensitive, OR-ed with the commands' `sensitive`; a throw counts as sensitive              |
+| `recallLimit`                                          | recall: the most lines kept; default 100 (`Infinity` keeps all, a fraction is rounded down)                |
+| `shouldRecord(line)`                                   | recall: whether a submitted line is recorded; default every line                                           |
+
+Run ids come from `createId` too, so with the default counter the first command's output is `c3` (`c1` the input entry,
+`c2` the run). An id `createId` returns that is already present throws from the method that caused it, as a duplicate
+id in `appendEntries` does.
+
+## State
+
+```ts
+interface ConsoleState {
+  entries: ConsoleEntry[]
+  input: { value: string; caret: number; revision: number }
+  running: {
+    runId: string
+    command: string
+    inputId: string
+    phase: 'authorizing' | 'running'
+  } | null
+  recall: string[] // oldest → newest (recall)
+  recallCursor: number | null // recall
+  recallDraft: string | null // recall
+  completion: CompletionSession | null // completion: candidates, active, the token's span, its original text
+  context: ContextFrame[] // bottom → top, root implicit (context)
+}
+```
+
+`getState()` returns the committed state, the same object until the next change. `running.phase` is `authorizing`
+while `beforeRun` has not answered. `input.revision` changes when the input element must be replaced: after a
+sensitive line ends, on `reset()` when the input was not empty, and on any programmatic clear of a non-empty input. An
+adapter keys its input element by it, so the element that held the text goes together with its undo history.
+
+## Methods
+
+Every console has:
+
+- `getState()`, `subscribe(listener)` (returns the unsubscribe function), `setOptions(updater)`.
+- `setInput(value, caret?)`: the consumer's programmatic write; the caret defaults to the end. Clearing a non-empty
+  input increments `input.revision`.
+- `editInput(value, caret)`: reports a user edit or caret move the element already shows; never increments
+  `input.revision` (a user backspacing to empty keeps the element). `setInput` and `editInput` do nothing while a
+  command runs.
+- `submit()`: ends the live input as Enter does. Resolves `true` after the run's end (at once when nothing runs: an
+  empty line, a parse error, an unknown command), `false` without doing anything while a run exists.
+- `run(line)`: replaces the live input with `line` and submits it; the same result as `submit()`.
+- `cancel()`: interrupts the running command, else ends the live line as cancelled.
+- `handleKey(input: KeyInput)`: applies the fixed key map; `true` when the key was handled, so the adapter prevents the
+  default.
+- `appendEntries(entries)` (an id already present throws), `clearEntries()`.
+- `getPrompt()`: the prompt of the next input entry. `isSensitive(line)`: whether `line` would be redacted.
+- `getCommands()`: the `CommandSpec` of each command that is not `hidden`, in registration order, each with `aliases`
+  (`[]` when it has none).
+- `reset()`, `dispose()` (below).
+
+The optional features add:
+
+- recall: `recallPrevious()`, `recallNext()` (each `false` when nothing changed), `clearRecall()`;
+- completion: `complete()`, `completeNext()`, `completePrevious()`, `acceptCompletion()`, `closeCompletion()` (each
+  `false` when it did nothing);
+- context: `pushContext(frame)`, `popContext(count?)`, `resetContext()`. `popContext` rounds `count` down; a count
+  below 1 does nothing, `Infinity` returns to the root. Frames are stored as given; the console does not check that
+  `data` is JSON.
+
+`KeyInput` is `{ key, ctrlKey, shiftKey, altKey, metaKey, isComposing, selection }`, where `selection` is `'none'`,
+`'input'` (text selected in the input) or `'document'` (text selected elsewhere inside the console). The adapter builds
+it from its event; the core never sees a DOM event. Tab on a non-empty input is always handled, even where nothing can
+be completed, so focus stays on the line.
+
+## Actions and notification
+
+An **action** is one synchronous change that starts from one trigger: a key, a method call, the settling of
+a promise (`beforeRun`, a command's `run`) or a `write()` call. A command run is several actions: its start, each
+asynchronous `write()`, and its end (fulfil, reject or cancel). Each action makes its changes on a working copy; at its
+end:
+
+1. each controlled slice that changed gets exactly one `on<Slice>Change(updater)` call, whose updater composes every
+   change of the action, in order, onto the value it is given;
+2. the internal slices are committed;
+3. subscribers are notified once.
+
+Nothing changes and nothing is called on creation. A method call or `write()` made while an action is open (synchronously
+from `run`, `beforeRun` or `isSensitive`) joins it; a synchronous return of `beforeRun` or `run` continues it. A call
+made from a change handler, `onClose`, `onError` or a subscriber comes after the commit and is an action of its own.
+An exception in a callback is reported through `onError(error, null)` and does not stop the other callbacks or the
+action's cleanup; without `onError`, or when `onError` is the thrower, it is rethrown asynchronously.
+
+A settle, `write()` or effect of a run that is no longer current (cancelled, reset, disposed, or replaced) changes
+nothing and calls nothing.
+
+## Controlled slices
+
+`entries`, `recall` and `context` are controlled when `options.state[slice]` is defined. The console then reads the
+slice from the options, never writes it, and reports each action's change through `on<Slice>Change(updater)`, where an
+updater is a value or a function of the old value. Hand the new value back with `setOptions`:
+
+```ts
+let entries: ConsoleEntry[] = []
+const console = createConsole({
+  commands,
+  state: { entries },
+  onEntriesChange: updater => {
+    entries = typeof updater === 'function' ? updater(entries) : updater
+    console.setOptions(old => ({ ...old, state: { ...old.state, entries } }))
+  }
+})
+```
+
+An action starts from the value the console last reported for the slice, until `setOptions` delivers a new
+`state[slice]` (that value wins, whether it accepts, refuses or edits the report; a defined `state[slice]` counts as
+delivered even when it is the same array) or the microtask after the report runs. That microtask is the only scheduling
+the core does. After it the base is `options.state[slice]` again. So two actions in one tick never lose each other's
+change, and a consumer that ignores a report gets its own value back on the next tick.
+
+An external change of `recall` ends recall browsing. An external change of `context` counts as a context change when
+the sequence of frame ids differs; a new array with the same ids is not one.
+
+## Lifecycle
+
+- `reset()` (one action): ends the running command as cancelled without an `interrupted` entry (the run is invalidated,
+  then its signal aborted), closes completion, and returns `entries`, `recall`, `context` and the input to their
+  initial values (`initialState`, else empty; for a controlled slice too). Each controlled slice gets one report.
+- `dispose()`: ends the running command the same way, runs every feature's cleanup once (an exception in one does not
+  stop the others), clears the internal state, and turns every later method into a no-op. Two consoles share nothing.
+
+## Contract
+
+The behavior rules are in [`contract/rules.md`](https://github.com/dolusoft/command-console/blob/main/contract/rules.md);
+the public API is in [`etc/command-console-core.api.md`](./etc/command-console-core.api.md).
+
+## License
+
+MIT, see [LICENSE.md](./LICENSE.md).