Commit Graph
90 Commits
Author SHA1 Message Date
james.maesandClaude Fable 5.1 a5e0cf4268 feat(assistant): qqq assistant ask and config, on a kernel Assistant module
The assistant qbit was reachable only through its generated operation
subcommands, which cannot read a streamed turn. The kernel now has an
Assistant module (feature probe, ask with the page context the way the
Next UI panel sends it, an incremental SSE parser and an answer fold with
numbers and links), and the CLI builds two first-class verbs on it:
`assistant ask` streams the answer and prints its numbers and links with
the command that opens each; `assistant config` says whether it answers
and with which model, or the server's reason (NOT_CONFIGURED names what
to configure).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 11:16:01 -06:00
james.maesandClaude Fable 5.1 981c0ca858 fix(core): linear-time history redaction; activity log reads on Windows
CodeQL flagged js/polynomial-redos (high) in the activity log's
redaction. Two regexes could backtrack polynomially on long arguments:
the header pattern (`Name:\s*(.+)`, slow on "A:" plus many spaces) and
the filter-criterion pattern (slow on long runs of name characters).
Redaction now uses linear scans:
- flags are parsed with indexOf at the first `=`
- headers and name=value pairs check the name before the first `:` or
  `=`
- filter text goes through a one-pass tokenizer (spaces, names, symbol
  operators, quoted strings, other runs), and the value after
  `<secret name> <operator>` is replaced
The remaining regexes each have a single, unambiguous quantifier.

Behaviour is unchanged on every existing redaction test. A differential
fuzz against the old code (300k random inputs, not committed) shows
three kinds of difference, none of which exposes a secret:
- a value now stops at a `)` that closes a group
- a quoted value is hidden whole
- a header whose value is only whitespace is left as it is
The rest of the differences are malformed mixed quotes.
New tests run 18 adversarial 100k-character inputs, each well under
500 ms.

The Windows lane failed "events are appended one JSON line each". The
test asserted POSIX mode 0600, and Windows has no mode bits. That check
now runs only off Windows. The reader splits lines on /\r?\n/, and a
new test reads back a CRLF file. The offset test now checks the parsed
time and the offset that getTimezoneOffset gives for that instant,
whatever the zone's name.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 11:11:47 -06:00
james.maesandClaude Fable 5.1 0bcc735ee9 feat: history of everything done in the CLI and the TUI
The owner asked for a "history" command that shows everything they have
done, like a bash history. Both heads now write to one activity log, an
append-only JSONL file per profile in the state directory
(~/.local/state/qqq/activity/<profile>.jsonl). Each event records the
time with the local offset, profile, server, client, kind, a one-line
summary and the command that does it again. The file is rotated once to
.1 at 5 MB. Secrets are written as ***: secret flags, name=value pairs,
filter criteria on secret or PASSWORD fields, Authorization headers and
bearer tokens. QQQ_HISTORY=off turns the log off.

- core: session/activity-log.ts (append, rotate, read, filter, redact,
  CLI kinds, mutating-command check).
- cli: every invocation is recorded on exit with its exit code and
  duration (shell completion is skipped). `qqq history` lists entries
  with --limit, --since, --grep, --kind, --all-profiles, --absolute,
  --commands and --format. `history rerun <n>` asks first for commands
  that change data and records the command it ran. `history clear`
  asks first.
- tui: one history.record(...) call at each site: `:` lines, opened
  apps, tables, records and processes, queries with filters, record
  create, edit and delete (no values), process outcomes, exports,
  prints, server switches, sign-in and sign-out. The History screen
  (`:history`, F9 > Work > History) filters as you type, Enter does an
  entry again, y copies and c or F8 clears. Ctrl+R on the `:` line is
  now a bash-style reverse search over the log.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 10:50:58 -06:00
james.maesandClaude Fable 5.1 7c66b16b6f fix(cli): table stats computes from matching records when the server offers none; quiet exit on a closed pipe
table stats refused tables without QUERY_STATS and pointed at --local. It now falls back
to the matching records itself (also when the columnStats process answers 403 or 404),
using the kernel computeLoadedColumnStats, says where the numbers come from, and exits 0.
--local forces it, --no-local keeps the old error, --max-records (default 10,000) caps it.

A reader that leaves early (qqq table query person | head -1) crashed the CLI with an
unhandled write EPIPE. stdout and stderr errors with EPIPE now exit 0 quietly, and a
stream pipeline rejected with EPIPE is not reported, so exports, process logs and
assistant ask behave the same.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 10:50:31 -06:00
james.maesandClaude Fable 5.1 c201f92f2b feat: stamp default export names with the local date and time
Why: two exports of the same table overwrote nothing but piled up as person.csv, person-1.csv,
person-2.csv, which say nothing about when they were taken. A default name now carries the local
date and time (person_2026-11-01_102316.csv), so exports are unique and sort by age.

One kernel helper, exportFileName(base, ext, now), is used by every surface that chooses a name:
table export, widget --csv and report route downloads, field saves from a record, the OpenAPI
document, and in the TUI the grid export, SQL Runner results, saved reports, widget exports and the
screen-text print fallback. A name the user gives (-o, a typed name in the file dialog) is left as
given; the dialog's name field is pre-filled with the stamped name. A name that comes from the
server keeps it unless it is taken, when the stamp goes before the extension (then -1, -2).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 10:34:13 -06:00
james.maesandClaude Fable 5.1 5d55f40127 docs: fix stale keys in the READMEs and let the readiness gate see default subcommands
F2 is Search, / is the find-anything palette, Ctrl+O switches servers and Ctrl+P prints; Ctrl+P no
longer steps to the previous record. The CLI README lists print, printer and profile. The readiness
gate reported qqq print person 1 2 as a missing verb although record is print's default command.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 07:40:04 -06:00
james.maesandClaude Fable 5.1 4bd62b7c1f feat(cli): add qqq print list and qqq print text
print list prints a table list of the whole result of the criteria (up to
10,000 rows) or one page, in the column order given, with paper and
orientation options; print text prints a file or stdin as a monospace
document. Both pick and remember the printer as print does and follow the
job.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 06:53:28 -06:00
james.maesandClaude Fable 5.1 d81c05352b feat(core): print table lists and text through the printing qbit
printTableList sends a grid's table, columns, widths, filter and sort with
the scope (all rows, this page, or selected rows) to printingPrintTableList
and passes the server's row-limit note on; printText prints text such as a
screen capture. listScopeChoices orders a grid's print choices: all rows
first when the grid is filtered or small, this page first otherwise, the
10,000-row limit named, and the selection as a list or as record sheets.
The client document's printing entry moves to 2.1.0.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 06:53:28 -06:00
james.maesandClaude Fable 5.1 437ed3c258 fix(tui): say plainly when the server cannot store attachments
Uploading to a server without the Object Storage QBit showed the raw
"IllegalStateException (The Object Storage qbit is not installed)". A
server failure (5xx) naming a missing QBit or extension now reads as one
line, for attachments "This server cannot store attachments: the Object
Storage QBit is not installed." (the kernel's missingQBitMessage, used by
the TUI's errors and the CLI's error output, so `collab
post-records-attachments` says it too). Once known for a server, the
UI's "+ Upload a file" row and the record's upload action are dimmed
with that reason instead of starting another upload.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 06:41:35 -06:00
james.maesandClaude Fable 5.1 0e07f8aefa feat(cli): qqq search shows the matched field, takes several tables and explains the syntax
The kernel gains record search (query/record-search): POST /search
grouped by table with counts, each hit's label, key and highlighted
snippet with the field, what the quick search query language supports
(AND of words matched from their start; no phrases, field:value,
wildcards or OR), notes for text that uses those, and the quick search
status line. The CLI's `qqq search` uses it: a `match` column, `--table`
repeated or comma-separated, `--limit` per table, a footer with the
tables and the total, `field:value` searching the value with a note, the
syntax in --help; `--json` prints the response.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 06:41:34 -06:00
james.maesandClaude Fable 5.1 cbabc31b5f feat(tui): mouse support across the whole TUI
The owner asked why the mouse did not work everywhere. Mouse tracking is now
on by default (button-event tracking with SGR 1006, no motion, so hovering
does nothing), switched by F9 Settings "Mouse: on/off" and :mouse (saved in
ui.mouse) or --no-mouse / --mouse for one run.

One transparent box over the terminal takes every event, so OpenTUI's own
text selection and focus never start; a registry of zones (rectangles
measured from the drawn elements, a layer per dialog) says what is under the
pointer. Clicks select, double-clicks activate, right clicks open the
actions at that row, the wheel scrolls 3 lines (Shift sideways in the grid),
header drags resize or move grid columns (saved as view settings), the
F-key bar presses keys and the footer opens the Servers dialog. Clicks
beside a dialog do nothing. Help and copyable-text dialogs say Shift+drag
selects text. The two-level F9 menu, the Servers dialog and the SQL Runner
panes are wired too.

The layer lives in src/mouse/*; screens add a few Zone wrappers.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 06:31:45 -06:00
james.maesandClaude Opus 5.5 d9317f5f59 feat(core,cli): profile short name, description and sign-in mode; qqq profile verbs
Profiles gain short (2-6 chars, for compact places), description, authMode
(auto, browser, device for OAuth2 servers), and lastUsedAt/user recorded by
the TUI. Every field is additive: a 1.0.0-rc.1 config.json loads unchanged and
its note shows where a description is missing. probeServer asks /version and
the authentication metadata with a short timeout so the CLI and the TUI's
Servers dialog report reachability the same way.

qqq profile list|add|edit|use|remove (also under qqq config profile) matches
the dialog field for field: --short, --description, --auth-mode, --check,
edit --server/--rename, list --probe.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 05:54:16 -06:00
james.maesandClaude Fable 5.1 c1e7bf9cfa feat(cli): add qqq print and qqq printer
qqq print <table> <id...> prints records as record sheets and follows the
jobs until they have printed (--printer, --copies, --no-wait, --timeout;
exit 1 when a job failed, 4 when still running at the timeout). qqq print
job list|status [--watch]|cancel follows and cancels jobs; qqq printer
list|use|show|forget|devices shows printers and print agents and manages
the printer remembered for the profile. Without the printing extension the
commands exit 5 with the installed list.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 05:49:03 -06:00
james.maesandClaude Fable 5.1 5cf62430aa feat(client): carry the printing 2.0.0 extension document
Appends qbit-printing's committed extension document (printing 2.0.0,
17 operations under /qbit/printing) to the client document with
merge-spec.mjs, keeping the other documents untouched, and regenerates the
schema and operation index (219 operations). The registry knows printing
with minimum 2.0.0: the realtime channel became the agent's prerequisite
there, so a 1.x server counts as not installed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 05:49:03 -06:00
james.maesandClaude Fable 5.1 536d0b37cd docs: record the enterprise sweep fixes and the -o convention for 1.0.0
CHANGELOG 1.0.0 gains the -o/--order convention with its migration note
and the extension table output under "Changed since 1.0.0-rc.1", and the
ESB trigger, login profile, health fallback and conformance fixes under a
new "Fixed since 1.0.0-rc.1". README, the cli and conformance package
READMEs, TRY-IT, the 1.0.0 release notes and the parity matrix (and its
generator) use --order for the sort and -o/--out for files.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 05:27:39 -06:00
james.maesandClaude Fable 5.1 248f30f458 fix(cli): name ESB triggers by process and fall back to an unadvertised /health
esb messages on a topic without --trigger only passed on the server's
"name one of the triggers", and trigger names look like
syncOrder.orderEvents, so the process name syncOrder answered 404. On a
400 or 404 the command now reads the ESB overview: a process name (or
label) with one trigger on the topic reads that trigger, several are
listed, and otherwise the error lists the valid trigger names
(resolveEsbTrigger in the kernel).

health get-summary said "not installed" on servers that serve /health
without listing the health extension in GET /version (qqq-all). The
kernel's probeHealth reads /health, shapes it like the extension's summary
and marks it unadvertised; the CLI shows it with a note when the
extension is not listed and the endpoint answers.

Tests cover the sub-table golden output, --columns, the -o convention,
ESB trigger resolution, the login warning and the health fallback against
a fake enterprise server.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 05:27:39 -06:00
james.maesandClaude Fable 5.1 5e34433a86 feat(cli): print extension results as key/value rows and sub-tables
The generated QBit commands (alerts get-inbox, sql-workbench
get-capabilities, collab get-..., api) printed lists as one line of JSON
in a key/value table (`items [{"id":5,...`). The kernel's render model
gains a document layout (formatDocument): scalars as aligned key/value
rows with nested objects as dotted keys, each list of objects as a
sub-table under its key with columns from the union of the row keys in
first-seen order, nested objects flattened one level, lists in a cell
joined, fitted to the terminal width (cells cut with an ellipsis, columns
that do not fit named under the table). render() uses it for nested
results and for any result given a layout; json, yaml, csv and text do not
change, and a --query reshape drops the column choice.

The inbox, notebooks, SQL history, comments, tasks, favorites and recents
get default columns (DEFAULT_LIST_COLUMNS); --columns (or the global
--fields) chooses, on the generated commands and on the first-class collab
comments list, favorites list, recents, tags list and people.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 05:27:39 -06:00
james.maesandClaude Fable 5.1 0687083c56 fix(cli): make -o the output file everywhere and the sort --order
table export and table query used -o for --order while the extension and
download commands used it for the output file, so `table export customer
-o file.csv` sorted by a field named after the path (and the server
answered 403). One convention now: -o/--out is always the output file, the
sort is --order (no short form; -s is --set). table export takes
-o/--out. On the commands that write no file (table query, saved-view
save, saved-report preview and set) -o still sorts for one release, hidden
from help, with a deprecation note. A sort field that looks like a file
path is warned about. Completion offers fields after --order only and
skips hidden options; the flat query alias forwards short-only options.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 05:27:38 -06:00
james.maesandClaude Fable 5.1 a10c8344d4 fix(cli): ask before login --server points an existing profile elsewhere
With QQQ_PROFILE set, `qqq login --server URL` silently moved that profile
to another server. resolveProfile now reports movedFrom when an existing
profile is given a different server; login warns, needs --yes (or a yes at
the question on a terminal) and says --profile <new-name> adds a profile
instead. saveLogin only moves a profile when login asked for it, so a token
refresh under a one-off --server no longer moves it either.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 05:27:38 -06:00
james.maesandClaude Fable 5.1 4d13ba98d2 fix(cli): keep the edit file path out of the editor's shell command
editText ran $EDITOR through a shell with a file name built from the table,
primary key and field, so a primary key such as $(...) executed. The path is
now the shell's $1 on POSIX (as git runs its editor) or a quoted variable on
Windows, and the name keeps only letters, digits and ._-.

Also: --api-path trimming and bulk help text use the linear core helpers.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 04:47:56 -06:00
james.maesandClaude Fable 5.1 5dd5e2d7f1 test: run the package tests without shell globs, for the Windows lane
The cli-windows-x64 lane failed in every package with "Could not find
...\dist\test\*.test.js": npm runs scripts with cmd.exe there, which
does not expand globs, and Node 20 does not glob its own arguments.
Plain "node --test" is no fix on Node 20 either, because its default
patterns run every file under a test directory, helpers such as
harness.js and stub.js included.

scripts/run-tests.mjs lists the *.test.js files directly in dist/test and
spawns node --test with them, so all four packages run the same files on
every platform. Counts on macOS are unchanged: 18, 167, 3 and 100.

Two cheap Windows fixes in the CLI test harness: the sandbox sets
USERPROFILE as well as HOME (os.homedir() reads USERPROFILE on Windows,
so defaults would have escaped into the real profile) and QQQ_STATE_DIR,
and the golden-file normaliser turns backslashes in sandbox paths into /
so export-download-dir.txt matches there too.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 04:39:55 -06:00
james.maesandClaude Fable 5.1 508ddc017a test(cli): assert dashboard widgets load concurrently, not within 3 s
The heavy-dashboard test proved concurrent loading by requiring the
whole command, CLI start-up included, to finish under 3000 ms against a
stub that answered each widget after 150 ms. A serial load would take
3.6 s, so the margin was 600 ms of start-up on whatever machine runs it:
the same kind of wall-clock guard that failed the release pipeline in the
core index test.

The stub now counts widget requests in flight and holds each answer until
every widget request has arrived (or 300 ms after its own arrival). The
test asserts the peak is above 1, which a serial loader cannot reach;
loadDashboard has no concurrency cap, so local runs also assert all 24
overlap and keep a generous 6 s bound, both skipped when CI is set.
Checked by making loadDashboard serial in the built kernel: the test then
fails with a peak of 1, CI set or not. Three npm test runs under
nice -n 19 with competing busy loops, and one with CI=1, all passed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 04:39:55 -06:00
james.maesandClaude Fable 5.1 1fd06db2e3 fix(cli): word doctor's UI API support from the same range as --version
qqq --version said "servers UI API >=1.6.0 <2.0.0" while qqq doctor said
"supports 1.6.0 to 1.8.0", which reads as if a 1.9.0 server were out of
range. The range is now built from UI_API_MIN_VERSION and a new
UI_API_MAX_EXCLUSIVE in version.ts, and doctor's ok, warn and fail details
all quote that UI_API_RANGE string. A newer-minor server (1.9.0) is
explicitly called supported while the warning about its new operations
stays. The comparison logic is unchanged: 1.6.0 and 1.8.0 are ok, 1.9.0
warn, 1.5.2 and a server without major 1 fail.

A test pins the range text, checks that --version and every doctor detail
use it, and keeps the old statuses.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 04:25:23 -06:00
james.maesandClaude Fable 5.1 1b0d54768c docs(packages): write npm READMEs for cli, client, core and conformance
The CLI and client READMEs were about a hundred words each, and the
conformance package had none, so their GitHub Packages pages said almost
nothing. Each now covers purpose, install (including the read:packages
token GitHub Packages needs), a quick start whose code was run against the
local sample server, the API surface, auth modes, compatibility and the
versioning policy, with absolute links back to the repository docs since
relative links do not resolve on a package page.

The core README gains install and quick-start sections and rows for the
26 modules the index exports but the table did not list. The TUI README is
corrected, not rewritten: qqq ui is in the release binaries only, and a
checkout runs it with node packages/cli/dist/main.js ui after npm ci.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 04:16:49 -06:00
james.maesandClaude Fable 5.1 d3d09622f9 build(packages): complete npm metadata on the four published packages
@qrun-io/qqq-ui-api-conformance had no homepage, bugs or keywords, so its
npm page would link nowhere, and the client was tagged "cli". All four
publishable packages now carry the same repository, homepage, bugs,
license and GitHub Packages publishConfig shape, with keywords that
describe each package. Versions are untouched; npm pack --dry-run shows
each tarball with dist, README.md and LICENSE and no tests or source maps.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 04:16:49 -06:00
james.maesandClaude Fable 5.1 34bbd2a317 release: 1.0.0 (client 1.8.0, core 1.0.0, conformance 1.6.0, cli 1.0.0)
All four packages go final together, with the exact workspace pins, so
the orb publishes them as latest. The CHANGELOG's rc.1 entry becomes
"## [1.0.0] - YYYY-MM-DD" (date to fill in on release day),
docs/release-notes/1.0.0.md is the release body with the final sequence
(tags v1.8.0 and cli-v1.0.0, gh release --latest, dist-tag latest), the
README, the CLI README and TRY-IT drop the rc version and @rc, and the
runbook says this branch is fast-forwarded onto main the day rc.1
feedback is accepted. node scripts/release.mjs --check is READY for
1.0.0.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 21:56:39 -05:00
james.maesandClaude Fable 5.1 f16b61f496 merge follow-up: keep the TUI's setup-widget pairs and sharing module, finding 28 linked
The base brought its own sharing module, a manageSession password sign-in and render-model
additions. The CLI now uses records/sharing.ts for qqq share, keeps its sessionId-cookie sign-in
as signInWithPasswordCookie next to the TUI's signInWithPassword, and the render model keeps both
sides: the web's wording and empty states from this branch, the TUI's pairs for the saved report
setup widgets (saved-report show still words them as the web does), its bar-chart default,
fieldValueList indents and block markers. Finding 28 is qqq#1359; SEC-030 also cites qqq-cli#10.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 20:40:22 -05:00
james.maes 6f52f6283d Merge branch 'feat/m1-kernel-cli' into feat/m1-cli-parity
# Conflicts:
#	docs/parity/feature-matrix.md
#	packages/core/src/widgets/render-model.ts
2026-10-31 20:36:49 -05:00
james.maesandClaude Fable 5.1 7bdf116010 core+cli: dashboards, widgets as the web renders them, home and find, reports, saved reports, sharing
The navigation, widget and report rows were the last open CLI rows. The kernel render model now
follows the web's widget contracts (multiStatistics values, location, usaMap, generic, cronUI,
dynamicForm, pivot and filter setups, rowBuilder, every composite block, table extras, chrome,
empty states, the dropdown message), and a loader fetches widgets as ConnectedWidget does:
metadata first (unknown or denied widgets cost no request), parent widgets load their children,
data bag and script viewers read their records, dashboards load every widget once at once.

On top: qqq home, qqq find, apps show --widgets, widget get --record/--run; report run through
the report's process (input fields, GET /download) or the report route; qqq saved-report
(show, preview incl. through an application API, run, set filter/sort/columns, pivot, schedule)
and qqq share for any shareable record. A WIDGET-adorned filter field in a process takes the
filter grammar. Printed filters no longer mark case-sensitive matches (the TUI builds criteria
without options, and its footers must not change).

The sample has no reports, saved reports or editor widgets; stub-server CLI tests cover them.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 20:31:14 -05:00
james.maesandClaude Fable 5.1 d62b6cd9d3 client+core+cli: TABLE_BASED sign-in, AUTH_0 audience, DISABLED tables and processes
TABLE_BASED servers could not be signed in to at all. The server's TableBasedAuthenticationModule
accepts HTTP Basic credentials on any route, inserts a session and answers with a sessionId
cookie; qqq login --username now does that once (password asked, or QQQ_PASSWORD), keeps only
the session and sends it as the sessionId cookie, which the typed client could not do, so the
CLI wraps its fetch. A refused password stores nothing; logout ends the session.

AUTH_0 servers were refused by the native sign-in discovery. The client now builds the sign-in
from the tenant, the native (or SPA) client id and the audience, which Auth0 needs to issue a JWT
the server can verify. No AUTH_0 server exists to run it against (finding 28).

DISABLED tables and processes come in the metadata with their permissions false; the CLI lists
them with the reason and refuses query, writes, copy (insert needed), bulk commands and process
run before any request, as the web explains the denial.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 20:15:00 -05:00
james.maesandClaude Fable 5.1 61c3a5694e core+cli: text matches send CASE_INSENSITIVE by default; findings 26 and 27
qqq ruled that CONTAINS, STARTS_WITH and ENDS_WITH are case-sensitive by design (finding 11,
qqq#1344) and that clients opt in per criterion with CriteriaOption.CASE_INSENSITIVE. The
grammar and quick search now add the option to every text match; ~= , OPERATOR:CS and
--case-sensitive ask for a case-sensitive match, and printed filters mark those with :CS.

The option does not reach the backend over v1 yet: QFilterCriteriaDeserializer ignores
options and the spec does not declare them (finding 27), so matching stays case-sensitive
until the server reads it. Finding 26 records the bulk mapping suggester problem the kernel
works around (it was cited as finding 11 by mistake).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 20:07:56 -05:00
james.maes 1bc1e4d122 Merge branch 'feat/m1-kernel-cli' into feat/m3-tui 2026-10-31 20:03:51 -05:00
james.maesandClaude Opus 5.5 cafbef1898 tui: record sharing, TABLE_BASED and PKCE sign-in, provider sign-out, session expiry
core: records/sharing.ts (share processes, audience, owner rule) and
signInWithPassword (TABLE_BASED via manageSession with Basic credentials,
nothing kept on refusal). cli: exports browser-login for the TUI.
tui: share dialog on shareable records and saved views (Z, :share);
TABLE_BASED username and password prompts; OAUTH2 sign-in in the browser
(authorization code + PKCE) with the device flow as the alternative;
sign-out ends the server session or the provider session; a 401 mid-use
opens sign-in on top and returns to the refreshed screen; :views.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 20:03:51 -05:00
james.maesandClaude Fable 5.1 decd6cd39f core+cli: record, query and process parity: columns, filter labels, variant memory, editors, copy, ad hoc widgets
Closes the record, query and process gaps the parity matrix listed. Each capability lands in
the kernel with tests and a thin command on top:

- possible-value labels in --where are resolved to ids, as the web filter sends them
- table columns keeps the query columns per table in the config the TUI column chooser uses
- the variant chosen for a table is remembered per server (--variant - forgets it)
- ad hoc composite widgets: conditional blocks, INPUT_FIELD blocks asked as step fields,
  BUTTON actionCodes offered as choices
- HTML fields show as text; table update -e edits HTML and code in $EDITOR
- CHIP values carry their color and icon (colored on a terminal; tables measure ANSI-free width)
- table get --copy, table api-call (the API playground), script test, table widget-form
  (a dynamicForm on a record form, saved in its merged JSON field)

Stub-server CLI tests cover what the sample cannot exercise (variants, saved views, audits,
application APIs, script tests, dynamicForm).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 19:58:52 -05:00
james.maesandClaude Fable 5.1 c798a0e0c4 docs+tests: bulk load parity rows, TRY-IT bulk section, stub-server CLI tests
The bulk rows (PRC-016, 029-034, 046, 058-061, QRY-031/032/034) are verified live against the
sample, except saved profiles, which the sample does not offer: those are covered by a stub-server
CLI test. The matrix script gains a blocked status (a note must cite a server finding) so the
release gate can tell a server limitation from unfinished work.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 19:37:47 -05:00
james.maes 12181ca183 Merge branch 'feat/m1-kernel-cli' into feat/m1-cli-parity
# Conflicts:
#	docs/server-findings.md
2026-10-31 19:30:54 -05:00
james.maesandClaude Fable 5.1 80deeb266f core+cli: bulk insert, bulk edit (with and without a file), bulk delete and saved bulk load profiles
Bulk load was the largest parity gap: the CLI could not load a file or change many records at
once. The kernel gains the bulk load model (table structure, v1 profile, mapping documents, the
server's suggestion cleaned per finding 11, mapping checks, diffs, upload templates) and
runBulkProcess, which drives the bulk processes through the runner with one callback per screen
(edit form, column mapping, value mapping, review), so the TUI can reuse it. Profile values go
as flat strings (fieldListJSON), cleared bulk-edit fields as "" (finding 23), and the file is
sent again after Back to the upload. BULK_LOAD_PROFILE_FORM no longer counts as an input, so the
result step is the last screen.

The CLI adds table bulk-insert, bulk-edit (--set/--clear, or --file with --key), bulk-delete,
table actions and bulk-profile list|show|save|rename|delete. Mapping comes from the server's
suggestion, a --mapping document (YAML/JSON), --column/--default, or -i prompts; the review is
shown, validation runs by default, and loading asks unless --yes (exit 2 without a terminal).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 19:30:35 -05:00
james.maesandClaude Fable 5.1 95b8d3a83c cli+tui: qqq doctor and qqq ui --check say which build is running
A first 'build' line names the version, the install (which binary, with
or without the UI, commit; or the npm package or a checkout), the
runtime (the Bun embedded in a binary, or Node) and the platform, so
support can read it from one paste. qqq --version adds the runtime too.
doctor's minimum UI API now comes from version.ts instead of a second
constant.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 19:09:53 -05:00
james.maesandClaude Fable 5.1 5ec288185b build: --with-tui bundles the terminal UI into the qqq binary
scripts/binary-with-tui.ts is a Bun-only entry that registers the
bundled TUI and starts the CLI, so the Node build is untouched. The
build installs OpenTUI's native package for every target (bun install
--os='*' --cpu='*' in packages/tui), pins OPENTUI_LIBC per Linux libc
and defines QQQ_BUILD_UI, which qqq --version prints as "with ui".
Source maps that bun writes beside each binary now go to
dist/sourcemaps/, so the release glob dist/qqq-* no longer uploads them.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:59:21 -05:00
james.maesandClaude Fable 5.1 588caf6203 cli: qqq ui says how to get the terminal UI instead of an internal path
In a binary or an npm install, qqq ui printed "looked for
/tui/src/main.tsx". It now says the TUI is not in this installation
and names the two ways to get it: a qqq binary built with the UI, or a
source checkout with Bun. A binary that bundles the TUI registers
globalThis.__qqqRunTui, and qqq ui hands over to it in-process with the
same arguments it would pass to bun run.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:59:21 -05:00
james.maesandClaude Fable 5.1 141b6513a6 cli: a question closed by Ctrl-D fails on Node 22.12 too
On Node 22.12, readline/promises leaves a pending question unsettled
when Ctrl-D closes the interface, so the prompt tests (and a real
prompt) hung until the event loop drained; that is the orb image. The
question now also settles when the interface closes: a usage error for
end of input, the caller's abort when it aborted. Ctrl-C still reaches
SIGINT (process run cancels, exit 130); checked on Node 20.20, 22.12
and 24.22 and with a real Ctrl-C and Ctrl-D at the clonePeople review.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:54:23 -05:00
james.maesandClaude Fable 5.1 29d848f822 Merge feat/m1-kernel-cli (bf859a5) into feat/m5-cli-release
Developer mode and the TUI batch (Home screen, search-first F9, the
metadata index, audits, tags and developer screens).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:52:33 -05:00
james.maesandClaude Fable 5.1 9c7efe606b core+cli+tui: collaboration tags; docs for Home, large instances, new keys
core: Collaboration.tags (vocabulary search), createTag, recordTags and
applyTags (add/remove in one request), with fake-transport tests.
cli: qqq collab tags list|add|remove|create (ids or labels).
tui: with the collaboration extension, a record shows its tags under the
header; t (F9 Tags…, :tags) opens the tag editor: remove with Delete, add
from the vocabulary searched as you type, create a new tag inline (a
suggestion on approved-only tables). Without the extension nothing shows
and :tags says it is not installed. The UI API has no rename or delete of
tags and no tag filter criterion, so those are not offered.

Verified live on the qbit-collaboration dev server (port 8098, separate
config dir, stopped afterwards): CLI list/add/create/remove, the TUI tags
line, the editor search, adding tui-test from the TUI.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:49:41 -05:00
james.maesandClaude Fable 5.1 7893dd465e Merge feat/m1-kernel-cli (4728702) into feat/m5-cli-release
Brings in the TUI package and the hardening review (createProgram in
program.ts, qqq doctor, the golden-output suite). Resolutions: main.ts
from the base; program.ts prints versionText(), whose second line now
starts with "UI API client <version>" as the golden test expects and
adds the supported server range; the CLI package keeps the release
metadata with the base's exports and its new conformance dependency,
and conformance goes to 1.6.0-rc.2 because the CLI now ships against it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:40:33 -05:00
james.maesandClaude Fable 5.1 fc6984661e Merge feat/m1-kernel-cli (hardening) into feat/m1-developer-mode
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:39:04 -05:00
james.maesandClaude Fable 5.1 bd219da46f cli: table apis, table api-doc, table developer; qqq script list, show, store, logs
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:38:35 -05:00
james.maesandClaude Opus 5.5 47287020b4 Merge feat/m1-kernel-cli (165c002) into feat/m1-hardening
Brings in the TUI stream (program.ts with createProgram and runCli, the io
object, qqq ui, session/login, local-state, filter completion, the result
cursor, the file navigator and env/doctor). Resolutions:

- main.ts is the base's thin entry; it still awaits the 0.1 credentials import.
- program.ts carries the option fixes (--version only, --server without -s)
  and registers qqq doctor.
- One set of ui helpers: the TUI's. readUiSettings/writeUiSettings are gone;
  qqq config set|get download-dir, upload-dir and download-mode use
  readFilePreferences/writeFilePreferences (ui.files), and the new
  qqq config set|get theme uses readTheme/writeTheme. readConfig keeps the
  corrupt-file refusal and unknown sections; the profiles test covers files,
  theme and an unknown section together.
- qqq doctor's terminal rows come from checkEnvironment, with formatReport
  under the table; --fix asks before each applyLiveFix and calls
  appendTmuxConf only after a y typed at a terminal.
- runCli and the prompts coexist (stdin is not a terminal in runCli, so
  prompts refuse; direct stdout writes are captured), tested in a child process.
- @qrun-io/qqq-ui-api-conformance is a dependency of the CLI package.
- The parity matrix is regenerated; docs/review-2026-10-31.md records each
  merge decision.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 18:37:51 -05:00
james.maesandClaude Opus 5.5 0bfdb06afe cli: table stats footer says how many values there are in all
"(3 values; of 5; --limit for more)" read badly; it is now
"(3 values; 5 in all; --limit for more)".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 18:32:58 -05:00
james.maesandClaude Fable 5.1 8b2ee7946c test: let the shell expand the test glob so npm test runs on Node 20
node --test only expands glob patterns itself from Node 21. With the
pattern quoted, Node 20 looked for a file literally named
dist/test/*.test.js and every workspace's npm test failed, although
the packages declare engines node >=20. The orb's Node 22 image hid it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:32:36 -05:00
james.maesandClaude Fable 5.1 99befbb2ef Merge feat/m1-kernel-cli (f364a3c) into feat/m3-tui
Parity matrix regenerated with both the CLI and the TUI statuses.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:29:18 -05:00