Commit Graph
12 Commits
Author SHA1 Message Date
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 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 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 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 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 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 0588e902fe release: 1.0.0-rc.1 metadata for the CLI, core and client packages
CLI and core go to 1.0.0-rc.1 and the client to 1.8.0-rc.2, with the
workspace dependencies pinned to them. Every published package now has
repository, homepage, bugs, engines (Node 20+), publishConfig, explicit
exports and a files list that leaves out compiled tests and source
maps. The repository LICENSE is copied in on prepack because npm only
packs a LICENSE from the package root. core had no publishConfig, so a
publish would have gone to the public registry; it now targets GitHub
Packages like the others. The CLI and client packages get the README
their files lists already named.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 18:28:04 -05:00
james.maesandClaude Fable 5.1 4660d50a8f cli: the program as a library (runCli) and the qqq ui command
main.ts becomes a thin entry over program.ts, which exports createProgram()
and runCli(argv, { stdout, stderr }): one command line run in-process with
its output captured, prompts off. The TUI's : command line uses it, so the
CLI grammar is the TUI's command language and both heads share one
dispatcher. Context output goes through an io object that runCli points at
the writers; the few commands that write to process.stdout directly are
captured for the duration of the run.

qqq ui [route...] runs packages/tui/src/main.tsx with Bun, passing the
profile, server, theme, --ascii, --linear and --mouse options and an
optional route in the CLI grammar.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 17:44:43 -05:00
james.maesandClaude Fable 5.1 8ed694cd2f cli: noun-verb grammar on the kernel, output formats, JMESPath, CRUD, api escape hatch
qqq <noun> <verb> for table (list, describe, query, count, get, create, update, delete, export),
process (list, describe, run) and job (list, get, logs, cancel, retry), with the 0.1 flat
commands kept as hidden aliases. Global --output json|table|text|csv|yaml, --json, --query
(JMESPath), --fields, --yes and --trace work before or after the subcommand. Filters take
--where, --group (AND/OR with parentheses), --or, --order, --filter-json, --print-filter and
--count; queries page with --limit, --skip and --all. qqq api <operationId> calls any
operation from the generated index (--path, --param, --body-json, --form, --bytes, --out).
Exit codes: 2 usage and bad filters, 3 auth, 4 unreachable or rate limited, 5 not found,
6 validation, 70 server error. The realtime stream can carry a session cookie for tail.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 17:03:18 -05:00
james.maesandClaude Fable 5.1 ff27af2f9e cli: session sign-in for MOCK and anonymous servers, sent as a cookie; qqq launcher
The client gains getAuthenticationMetaData, createSession (reads the HttpOnly sessionUUID
cookie) and a sessionCookie option; UI_API_VERSION is 1.8.0. qqq login branches on the
server's authentication type and stores a server session for MOCK and FULLY_ANONYMOUS; the
device flow stays for OAUTH2 and AUTH_0. The session goes as a cookie because a bearer
session cannot continue asynchronous process steps on the 4.1.0-SNAPSHOT sample server.
scripts/dev/qqq.sh runs the CLI from source so every commit is testable without a build.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-31 16:21:02 -05:00
james.maesandClaude Opus 5.5 ea79ddeb78 feat: reference CLI, generated UI API client, conformance suite and dev IdP
- @qrun-io/qqq-ui-api-client: typed client generated (openapi-typescript +
  openapi-fetch) from the merged UI API document; device-flow sign-in, refresh,
  UiApiError (BasicErrorResponseV1), SSE reader
- @qrun-io/qqq-cli: qqq login/whoami/apps/tables/query/get/run/jobs/tail,
  only through /qqq/v1 with Authorization: Bearer
- @qrun-io/qqq-ui-api-conformance: black-box suite + qqq-dev-idp
- scripts/merge-spec.mjs, Prism mock, CI and GitHub Packages publish workflows

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 11:47:12 -05:00