refactor: rename stax plans to stax work-items - #40

Aligns the web UI with the renamed artifact noun (PR #40 moved the
CLI from `stax plans` to `stax work-items`). The user-visible URLs,
nav rail labels, page identifiers, and the HTTP API the page TS
consumes all migrate together so the naming axis is one consistent
"work item" everywhere.

Frontend:
- Page files: scopes.html → work-items.html, scope.html → work-item.html;
  scopes.ts → work-items.ts, scope.ts → work-item.ts. Layout block-helper
  args (title/page/active) updated to match.
- Nav rail (header.html + mobile-nav.html): "Scopes" → "Work items";
  href /scopes → /work-items; data-active-key follows. Flag icon kept.
- Detail page back-link, list-page empty-state, home-page card +
  Latest section, /search results section, and all DOM ids that
  embedded "scope" (`#scope-icon`, `#scope-title`, `#scope-body`,
  `#scopes-list`, `#latest-scopes`, `tpl-scope`, `tpl-scope-link`)
  renamed to the work-item equivalents.
- Page dispatcher in bundle.ts uses bracketed keys for the
  kebab-cased page names; vite.config.ts pages array follows.
- Internal hrefs `/scope?id=…` → `/work-item?id=…` across home.ts,
  search.ts, system.ts.
- CSS: `.scope-body` → `.work-item-body`.

HTTP API + Go server:
- /api/scopes → /api/work-items, /api/scope → /api/work-item;
  apiScopesPath/apiScopePath constants renamed.
- Handler renames: handleAPIScopes → handleAPIWorkItems,
  handleAPIScope → handleAPIWorkItem; readScopesForAPI →
  readWorkItemsForAPI.
- Struct renames (with collision resolution): scopeListItem →
  workItemListItem, scopesListResponse → workItemsListResponse,
  scopeRelation → workItemRelation, scopeDetail → workItemDetail.
  The previous `workItemDetail` (per-system-row inner type used by
  /api/systems?id=) renames to `systemWorkItem` to free the better
  name for the detail response.
- JSON wire keys: `"scopes"` → `"workItems"` on statsResponse,
  workItemsListResponse, searchResponse, and systemEntry. Frontend
  TS types follow.

Tests / docs:
- server_test.go: clean-URL fallback expects /work-items and
  /work-item; every fixture/assertion updated to body.WorkItems
  and `"workItems":` wire shape.
- scripts/e2e_test.sh + e2e_test.ps1: curl + assert_contains paths
  and JSON-key substring assertions updated.
- AGENTS.md: frontend hard rules now reference /work-item URL,
  #work-item-body, active="work-items", and {workItems: [...]}.
- frontend/package-lock.json: regenerated with `npm install
  --include=optional` (same pre-existing @emnapi gap PR #40 hit).

Verified locally: go vet + go test clean, npm run check clean,
scripts/e2e_test.sh 624/624 cases pass.

Signed-off-by: Tanzim Saqib <[email protected]>

* refactor(frontend): rename /scopes route to /work-items

Aligns the web UI with the renamed artifact noun (PR #40 moved the
CLI from `stax plans` to `stax work-items`). The user-visible URLs,
nav rail labels, page identifiers, and the HTTP API the page TS
consumes all migrate together so the naming axis is one consistent
"work item" everywhere.

Frontend:
- Page files: scopes.html → work-items.html, scope.html → work-item.html;
  scopes.ts → work-items.ts, scope.ts → work-item.ts. Layout block-helper
  args (title/page/active) updated to match.
- Nav rail (header.html + mobile-nav.html): "Scopes" → "Work items";
  href /scopes → /work-items; data-active-key follows. Flag icon kept.
- Detail page back-link, list-page empty-state, home-page card +
  Latest section, /search results section, and all DOM ids that
  embedded "scope" (`#scope-icon`, `#scope-title`, `#scope-body`,
  `#scopes-list`, `#latest-scopes`, `tpl-scope`, `tpl-scope-link`)
  renamed to the work-item equivalents.
- Page dispatcher in bundle.ts uses bracketed keys for the
  kebab-cased page names; vite.config.ts pages array follows.
- Internal hrefs `/scope?id=…` → `/work-item?id=…` across home.ts,
  search.ts, system.ts.
- CSS: `.scope-body` → `.work-item-body`.

HTTP API + Go server:
- /api/scopes → /api/work-items, /api/scope → /api/work-item;
  apiScopesPath/apiScopePath constants renamed.
- Handler renames: handleAPIScopes → handleAPIWorkItems,
  handleAPIScope → handleAPIWorkItem; readScopesForAPI →
  readWorkItemsForAPI.
- Struct renames (with collision resolution): scopeListItem →
  workItemListItem, scopesListResponse → workItemsListResponse,
  scopeRelation → workItemRelation, scopeDetail → workItemDetail.
  The previous `workItemDetail` (per-system-row inner type used by
  /api/systems?id=) renames to `systemWorkItem` to free the better
  name for the detail response.
- JSON wire keys: `"scopes"` → `"workItems"` on statsResponse,
  workItemsListResponse, searchResponse, and systemEntry. Frontend
  TS types follow.

Tests / docs:
- server_test.go: clean-URL fallback expects /work-items and
  /work-item; every fixture/assertion updated to body.WorkItems
  and `"workItems":` wire shape.
- scripts/e2e_test.sh + e2e_test.ps1: curl + assert_contains paths
  and JSON-key substring assertions updated.
- AGENTS.md: frontend hard rules now reference /work-item URL,
  #work-item-body, active="work-items", and {workItems: [...]}.
- frontend/package-lock.json: regenerated with `npm install
  --include=optional` (same pre-existing @emnapi gap PR #40 hit).

Verified locally: go vet + go test clean, npm run check clean,
scripts/e2e_test.sh 624/624 cases pass.

Signed-off-by: Tanzim Saqib <[email protected]>

* chore(ci): rename test workflows to E2E test naming

User-driven rename of the test workflow names — the two top-level
workflows (Linux and Windows) now share an E2E test prefix for
visual grouping in the GitHub Actions sidebar.

Signed-off-by: Tanzim Saqib <[email protected]>

---------

Signed-off-by: Tanzim Saqib <[email protected]>

Commit 8ed25f9 (#40) renamed the artifact concept project-wide but the
text-substitution pass missed three classes of identifiers in
`skills-evals/`, all of which break the pytest run end-to-end:

  1. A list-comprehension f-string `[p.slug for p in plans]` got
     rewritten to `[p.slug for p in work items]` — two tokens with a
     space, so Python aborts at parse time. Twelve test files all
     share this identical pattern (every backend's
     `*_reminders_supersedes_todo.py` and `*_work_item_extends.py`),
     so every workflow that runs pytest hits the same collection-time
     SyntaxError on the first import.
  2. `skills-evals/src/skills_evals/workspace.py` still exports
     `load_all_plans` / `ParsedPlan` / `collect_plan_files` /
     `_parse_plan`. Every test file already imports
     `load_all_work_items` from that module, so once the SyntaxError
     is fixed the next collection error is an `ImportError` of the
     same shape — i.e. all twelve workflows would still fail.
  3. `skills-eval-cline.yml`, `skills-eval-cline-user-scope.yml`,
     `skills-eval-copilot.yml`, and `skills-eval-copilot-user-scope.yml`
     still pass `tests/test_<agent>_plan_extends.py` to pytest, but
     the rename moved that file to `tests/test_<agent>_work_item_extends.py`.
     With pytest's default selector (`--strict-config`) a missing
     path is a hard failure, so all four cline/copilot workflows
     fail before collection even starts.

Single bundled fix because the three layers are coupled — fixing any
one alone still leaves CI red. Verified locally that
`uv run pytest --collect-only` collects 25 tests with zero errors
(20 deselected by the existing agent filter, 5 collected for
`STAX_AGENT_KEY=claude`).

The judges' user-facing label (`name="PlanQuality"` in
`work_item_judge.py`) is intentionally left alone — it appears in
DeepEval output, not the wire, and renaming it would also drift the
historical score series.

Signed-off-by: Tanzim Saqib <[email protected]>