@colony2/cortex 0.0.34 → 0.0.36

package/README.md

@@ -9,6 +9,35 @@ Cortex connects to a remote [JobDB](https://github.com/colony-2/jobdb) server.
 Run c2j workers separately against the same JobDB. Projects in the UI are JobDB
 tenants; cells are the current Git repository and its c2j-configured dependents.
 
+## Goal list filters and search
+
+The Status column's filter matches the badges shown for jobs, including Succeeded,
+Failed (application/system), Timed out, and Cancellation requested. Multiple
+selections match any selected status. All statuses start checked; uncheck individual
+items or use Select all / Select none, then Apply. Selecting none shows no jobs.
+Finished (outcome unavailable) matches
+completed jobs with no stored outcome; retrying jobs retain their scheduling
+status even if a previous attempt failed. The Cell column uses the same checkbox
+controls, with all cells selected initially. Its choices come from cell names in
+the returned jobs, including Unknown cell for missing names, rather than the server's
+configured cell catalogue. Cell filtering runs in the browser on the current page;
+unchecked cells remain available in the menu. Status filtering runs across pages.
+
+Search full prompts at the right of the Cancel/Delete row, including text beyond the shortened row
+label and prompts from other loaded attempts. Click the Goal, Status, Cell, or
+Submitted column header to sort ascending or descending; click again to restore
+the original order. Search and sorting run in the browser on the current page.
+Search, sorting, and filters persist in the URL when opening a goal and returning.
+
+The jobs API accepts repeated `displayStatus` parameters for these states, for
+example `?displayStatus=READY&displayStatus=failed_app`. The existing `status`
+parameter still filters raw scheduling states; the two parameters cannot be
+combined. Display filtering scans compact JobDB pages without loading job
+details. Each request scans at most 20 backend pages, so a sparse or empty result
+can still have a `next_page_token`; use **Next jobs** to continue.
+Repeated `cell` parameters (for example `?cell=alpha&cell=beta`) match jobs from
+either cell's repository before pagination; a single `cell` works as before.
+
 ## Chapter downloads
 
 On a job's story page, **Download chapters** saves a JSON inspection export of
@@ -162,8 +191,27 @@ pnpm --filter @colony2/app test:e2e --project=production recipe-input.spec.ts
 node --test npm/cortex/test/*.test.cjs
 ```
 
-Playwright installs Chromium if missing. On a fresh Linux host, first run
-`pnpm --filter @colony2/app exec playwright install-deps chromium`.
+The c2 execution tools in [`.c2/config.yaml`](.c2/config.yaml) declare Go, Bash,
+Make, Node.js, pnpm, Playwright, Chromium, and FFmpeg. Nix supplies Chromium's
+runtime libraries and fonts. The browser tests use Chromium and FFmpeg from
+`PATH`, without downloading browsers or installing system packages.
+
+Outside c2, either provide Chromium and FFmpeg on `PATH`, or install Playwright's
+browser before running the tests:
+
+```sh
+PLAYWRIGHT_BROWSERS_PATH="${CORTEX_PLAYWRIGHT_BROWSERS_PATH:-$HOME/.cache/ms-playwright}" \
+  pnpm --filter @colony2/app exec playwright install --with-deps --only-shell chromium
+```
+
+The Nix Chromium package targets Linux workers; macOS developers can use the
+Playwright installation command above.
+
+Setting `CORTEX_PLAYWRIGHT_BROWSERS_PATH` selects that Playwright installation
+even when system browsers are on `PATH`, as in CI. Otherwise, system executables
+are used only when both Chromium and FFmpeg are available; an incomplete pair
+falls back to Playwright's browser cache.
+
 The suite manages its own servers on ports 15173 and 18081–18083. It covers
 submission, stories, tenants, cells, and input events. The production tests use
 HTTP JobDB backed by temporary SQLite storage.
@@ -182,12 +230,9 @@ is mapped to that repository in the worker's environment. No API or EventSource
 mocks are used in these tests. Worker logs and recipe outcomes are attached to
 the Playwright report in `web/app/playwright-report`.
 
-The timeout regression also runs against the real worker. It currently records
-an **expected failure**: with the pinned c2j / JobDB versions, an unanswered external
-input task remains pending past its recipe deadline. Step deadlines have the
-same limitation. The test first verifies that the prompt appears, then marks
-only a confirmed still-pending outcome after the deadline as expected; setup
-and other failures still fail CI. Timeout handling needs an upstream JobDB fix.
+The timeout regression also runs against the real worker. It verifies that an
+unanswered input expires, clears pending prompts in both browser tabs, and rejects
+late submissions.
 
 ## Releases
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@colony2/cortex",
-  "version": "0.0.34",
+  "version": "0.0.36",
   "description": "Web interface for c2j recipe jobs",
   "license": "UNLICENSED",
   "homepage": "https://github.com/colony-2/cortex",