Test runs stay quiet by default. Diagnostic logs can be enabled explicitly when troubleshooting, while normal application logging and saved scenario output remain available.
Resolves#22.
---------
Co-authored-by: ars9 <ars9@pm.me>
Co-authored-by: agent <agent@halstation.halstation.local>
Reviewed-on: #25
Co-authored-by: agent-codex <agent-codex@ars9.space>
- Exercise CLI provisioning through browser/API/MCP auth, run events, logout, and deletion.
- Allow integration coverage to reopen the same file-backed test database.
- Add account, JWT session, revocation, cookie and bearer handling.
- Protect server surfaces while preserving public health, manifest and disabled mode.
- Add SQLite migration and focused server regression coverage.
- GET /scenarios/:id/export-e2e and the export_e2e_test MCP tool take
an optional version, defaulting to the latest
- build the test project from that version's steps, name and timeout
- put the version in the zip name (<scenario>-vN-e2e-test.zip), the
generated package name and the README heading
- the Export e2e test button exports the version being viewed
- document the e2e export in scenario.md and mcp.md
- reopen the run events stream with backoff when the browser closes it for good (Firefox drops quiet connections after a network change)
- enable notifications when the permission is granted outside the bell, unless turned off explicitly
- follow permission changes made in the browser's site settings
- highlight the bell while notifications are on
- add RunEventsService and emit run.started / run.finished from the scheduler
- stream run events over SSE at GET /api/v1/scenarios/runs/events with a heartbeat
- add useRunNotifications hook and NotificationToggle (opt-in bell in the side panel footer)
- refresh runs lists when a run finishes
- document the events stream and notifications
Closes#12
- request the exact version being exported via ?version=N so file
content always matches the filename
- name downloads <scenario>-v<N>.yaml and snippet-<alias>-v<N>.yaml
- read answers from /dev/tty: under `curl ... | bash` stdin is the
script itself, so `read` consumed the script's own lines; fall back
to defaults when there is no terminal
- check that docker, the compose plugin and the daemon work and that
compose accepts the generated compose.yaml
- start liqa with `docker compose up -d` in the install directory,
printing the manual start command if a check or the start fails
- examples/self-test: importable scenario, snippets, credential and
environment that test the liqa instance they run on
- CI builds the Docker image only for vX.Y.Z release tags
- bump version to 1.24.3
- add examples/ with a ready-to-import self-test: environment, credential,
snippets and a scenario that creates, runs and checks another scenario
through the liqa REST API and UI, then cleans up
- add test/examples.spec.ts: imports every example and parses its code
- link the examples from README, docs/scenario.md and CLAUDE.md
Closes#6
- trigger the image job on vX.Y.Z tag pushes instead of master pushes
- run server and client checks unconditionally on tags before the build
- fail the build when the tag doesn't match the package.json version
- document the release routine: version bump, changelog and tag are
done on master after work branches are merged
- large run log data blocks start collapsed, with per-block and
expand/collapse-all toggles; limits set by RUN_LOG_DATA_COLLAPSE_BYTES
and RUN_LOG_DATA_COLLAPSE_LINES
- copy logs button copies the filtered logs as plain text
- GET /manifest.json serves the app version and public client settings,
cached by the UI in localStorage
- bump version to 1.24.2
- collapse run log data blocks whose pretty-printed JSON exceeds a byte
or line limit, with a per-block toggle and an expand/collapse-all
button next to the Logs heading
- align data blocks and toggles with the context/message column
- add a "Copy logs" button that copies the filtered logs as plain text
with every data block expanded
- add GET /manifest.json with the app name, version and run log data
limits (RUN_LOG_DATA_COLLAPSE_BYTES / RUN_LOG_DATA_COLLAPSE_LINES)
- load the manifest in the client stale-while-revalidate: localStorage
copy first, refetched per page load and on tab focus after a while
- show the server version in the sidebar footer, with a reload hint
when it differs from the client build
Closes#3
- "Step N passed" log entries carry the step's return value as data
- context.assert takes an optional details argument stored as log data
on failure; step and snippet failure entries name only the assertion
- log output shows elapsed time in whole seconds
- run artifact and scenario file names open the file in a new tab
- bump version to 1.24.1
- "Step N passed" log entry carries the step's return value as data
- context.assert accepts an optional details argument; on failure the
assertion:fail entry stores { details, error } as data
- assertion failures throw AssertionFailedError so "Step N failed" and
"Snippet X failed" entries name only the assertion, without repeating
the details; the step run description keeps the full message
- exported e2e runtime accepts and prints assert details
- log output shows elapsed time in whole seconds, matching the stored
timestamp resolution
- run artifact and scenario file names link to the inline file content
in a new tab
- step and snippet editors open a reference of the script runtime and
its context API from a (?) button next to the Code label
- bump version to 1.24.0
- a (?) button next to the Code label on the step and snippet
create/edit pages opens a reference of the script runtime: globals,
every context member with examples, and pitfalls such as awaiting
getStepOutput and assert
- the reference lives in components/modals/code-help.md and is
rendered as markdown
- Modal takes size="lg" for document-like content; the dialog is
capped to the viewport and its body scrolls, focusable when lg so
the keyboard can scroll it
- docs/scenario.md notes that getStepOutput is async and points to
the in-app reference to keep in sync
- scenario run log entries carry a context (step/snippet/assertion/run)
and a data payload split out from the message, plus a new debug level
- run detail page shows the full log list in a terminal-style viewer
instead of a paginated table
- bump version to 1.23.0
- context.log/warn/error and console.* split arguments: strings join
into message, object/array args are kept out of it and stored as
the log entry's new data column (JSON), so message stays a stable
string regardless of an object's shape
- added a debug log level alongside log/warn/error, including
context.debug() and console.debug() (previously folded into log)
- CSV/Markdown run log export include the data column/block
- LogOutput renders data pretty-printed in a separate block below
the message, and dims debug entries with a dedicated grey token
calibrated to the WCAG AA contrast floor
- scenario_run_logs gains a context column (step:N, snippet:alias,
assertion:pass/fail, run), tracked through a call stack in
CodeExecutorService so nested runSnippet calls tag their own and
inner log lines
- automatic step started/passed/failed entries and the Playwright
trace upload notice are tagged accordingly
- run log export (CSV/Markdown) and the logs search match context
as well as message
- add a LogOutput UI component: a terminal-style log viewer with
level color coding, elapsed-time-since-start timestamps and a
context tag, replacing the generic Table on the run detail page
- show the full log list instead of paginating it, capped to a
scrollable block
- fix migrations.spec.ts's revert test, which only undid the last
migration instead of all of them