0.1.0-dev.1

Banora CLI

An optional Node 24.x terminal consumer of the Banora SDK. Agents operate on logical board state and SGF with JSON requests/responses, without vision, a browser, an LLM service or a framework. Initial 0.1 release.

Local Use and Installation

Install the SDK and CLI, then discover their contract:

npm install @0disoft/banora @0disoft/banora-cli
npx --no-install banora schema

In the repository, run bun install, then bun run build:cli. Run commands as bun run cli --help, bun run cli schema or directly as node packages/cli/dist/main.js schema. The direct Node form produces only JSON on stdout; package-manager command banners are not CLI response content.

To install built artifacts in another project, create SDK/CLI tarballs with bun pm pack --ignore-scripts from their respective package directories, then install both with npm install /absolute/path/sdk.tgz /absolute/path/cli.tgz (use their actual filenames). Invoke the installed executable with npx --no-install banora --help. SDK peer resolution is verified with npm. The tarball route uses exactly the artifacts you provide.

Discover First

banora --help returns command/flag discovery and exit codes as JSON. banora schema returns the immutable JSON Schema for every request/operation. banora --version returns package version JSON. No command prompts interactively. Requests use schemaVersion:"banora.automation/v1"; results contain ok and either data or structured error:{code,message,operationIndex?,reason?}. Schema discovery itself returns a JSON Schema rather than a result envelope.

create also accepts --operations; create/inspect/edit accept --profile with japanese-territory, aga-territory, aga-area or tromp-taylor. For initial selection and all other options, use the full JSON run request. Default rules remain the SDK's simple-ko/suicide-forbidden policy. Choose a scoring profile explicitly when requesting a score.

Example request.json:

{
  "schemaVersion": "banora.automation/v1",
  "kind": "record",
  "size": 9,
  "operations": [
    { "op": "play", "point": { "x": 4, "y": 4 } },
    { "op": "comment", "text": "Reviewed by an agent" },
    { "op": "legal-points" }
  ]
}

Run banora run --request request.json --output reviewed.sgf, or pipe that JSON to banora run. Using files/stdin avoids shell-dependent escaping. Coordinates are zero-based from the top left; null play points mean pass. Record locators use {gameIndex,path:[childIndex,...]} against the current tree. Results expose the portable selected locator, properties/children, row-major stones, rules/captures, logical annotations, history flags, query results and SGF.

Search and Review Multiple Comments

Run banora search --input game.sgf --query text --properties C,N,LB --limit 20. --properties is a comma-separated list of uppercase SGF identifiers. Omit --query (or pass an empty query) to list nonblank values. Optional --game uses a zero-based game index; --offset paginates matches and --case-sensitive requests exact case. Queries cover every game/variation, including moves beyond the visible Studio tree limit. They change no selection/history or files. Follow results[0].value.hits[].target through JSON goto or use it as a batch target. Exact bounds are in the schema and automation contract.

An operations file can preview changes:

[
  {
    "op": "comment-batch",
    "previewOnly": true,
    "changes": [
      {"target": {"gameIndex": 0, "path": [0]}, "text": "Reviewed", "expectedText": "Original note"},
      {"target": {"gameIndex": 0, "path": [0, 0]}, "text": "", "expectedText": "Obsolete note"}
    ]
  }
]

Run banora edit --input game.sgf --operations preview.json to inspect results[0].value.edits. To apply, omit previewOnly (or use false), add the preview response's canonical sgf as operation expectedSgf, and use an explicit new output file. That guard rejects any intervening content change. expectedText alone guards only each targeted comment. Apply is one request-local Undo unit; append an undo operation in that same request to reverse the entire batch. Wrong targets/conditions or exceeded limits publish no output file. Files/stdin are bounded to 8 MiB, including duplicated expected SGF in a guarded request.

Reusable Requests

banora recipe lists original named workflows and expected success/failure. banora recipe --name create-study returns a complete banora.automation/v1 request; save it as UTF-8 JSON or pipe it into banora run. Discovery executes nothing and never interprets a name as a file. Included names are create-study, inspect-branches, review-preview, score-agreed and the intentional failure fixture occupied-point (exit 3 when executed). Review/replace authored SGF, coordinates, changes and scoring agreement before adapting to real work.

The requests are embedded in the built CLI, so they also work in an independently installed tarball. Save response checkpoints separately from SGF output. Preview responses require an explicit approved request with unchanged expectedSgf to apply; scheduling, concurrent-file authority and live-app permissions stay host-owned. See the workflow guide for checkpoint resume, preview/apply/Undo and bounded retry examples.

Diagnostic Reports

Run banora diagnose --request request.json --output diagnostics.json to reproduce one isolated request without returning edited SGF, snapshots, comments, queries, paths or raw errors. The JSON envelope is banora.cli-diagnostics/v1, with ok, diagnostics, optional zero-based failed operationIndex, rounded SDK execution durationMs and transport error.code. Environment contains Node major/platform family only. SDK operation events are untimed and summaries cover retained events, up to 256; check dropped for eviction.

Unlike ordinary authored-output commands, --output saves a diagnostic report even when the SDK request fails (exit 3). Success exits 0. Usage/read/JSON failures exit 2 and do not publish a file. Output failure exits 4 with SDK evidence retained; transport errors include no message/path. Existing outputs require --force; inputs/aliases remain protected. File/stdout report contents match. No authored file is changed or data uploaded. Invocation opts in for that run; inspect before sharing and delete downloaded reports separately. Full stage/recovery definitions are in the diagnostic contract.

Operation names: play, previous, next, goto, comment, marker, setup, connection, stroke, remove-stroke, clear-strokes, remove-branch, reorder-branch, undo, redo, legal-points, score, search, comment-batch. Exact fields are in banora schema; unknown/repeated CLI flags and unknown request/operation fields are errors. Score output depends on manually agreed dead/seki status, not automatic life-and-death detection.

Output, Errors and Ownership

The executable writes exactly one JSON document plus newline to stdout, including errors; callers check the exit status and ok. Exit statuses: 0 success, 2 usage/ read/JSON/size limit failure, 3 SDK validation/command failure, 4 output-save failure. Input reads are bounded to 8 MiB; SGF retains its own 5 MiB/parser limits and JSON batches have at most 256 operations. All batches run on a disposable private controller. Legal-point scans share an 8,192-candidate-cell per-request budget. Whole-record searches and comment batches share eight calls per request. A failed batch exposes no partly edited record and writes no output.

Without --output, nothing is saved. Successful --output PATH saves SGF for a record or normalized snapshot JSON for external state. Publication uses a complete temporary file beside the output, exclusive by default. Existing outputs require --force; input paths/realpath aliases remain protected. Filesystem failures have an output error; stdout alone does not imply the file was saved. Inputs remain unchanged, including SGF unknown-property semantic preservation. SGF byte input follows the SDK's declared-encoding decoder; JSON is UTF-8.

Each invocation is independent. Undo/Redo and IDs are request-local; persist SGF and portable locations for later invocations. The default snapshot key local-record is not a host revision: provide stateKey when integrating a host. External snapshots are inspected only; the CLI never approves intentions or automatically controls a mounted application. Hosts own live-state permissions, revisions, transport and engine integration. SVG/PNG browser view exports remain DOM APIs; the CLI's headless output formats are structured state and SGF.

See the full automation contract. bun run smoke:cli checks isolated npm tarball installation, the installed bin and actual Node process/stdin/error/output behavior; it does not require a browser.