FM-925 — Skills console: matrix, machine tab, catalog editor, presets, search

[Andreas-Froyland]

Epic: #120 · Depends on: FM-920, FM-921, FM-922, FM-923

Context

The skills backend (FM-920–923) needs its console.

Goal

A Skills page with the fleet matrix (per-agent deployment, version, update, drift), a machine Skills tab (library/presets/deployments + actions), a catalog editor (Markdown with frontmatter validation, version diff, assignment editor, rollout plan preview, publish & roll out), presets, and skills.sh search.

Architecture reference

docs/planning/web-console.md (Skills); mockup skills.html.

Dependencies

FM-920, FM-921, FM-922, FM-923

Research required

None.

Acceptance criteria

• Remove/adopt/rollout show dry-run or plan previews before mutation
• Conflict and held-back paths shown as data with the documented ways out

Non-goals

• Editing machine-local skill content until FM-S10's contract exists

Tests

Component tests (matrix states), e2e for edit→publish→rollout against the stub API.

[Andreas-Froyland]

Implementation approach (Claude)

UI-only, over the existing skills API (FM-920–923). No backend changes.

• /skills page (apps/web/src/pages/skills/), tabs:
  • Fleet matrix — GET /skills/matrix joined with machines. Rows are skills, grouped by Fleet catalog (the skill name matches a catalog entry) vs machine-local (not managed by Fleet). Cells show per-agent deployment, update-available, and no-CLI/stale/unsupported states. Filters cover agent and state.
  • Catalog — list plus editor for Fleet-authored entries:
    • SKILL.md editor with client-side frontmatter validation mirroring fleet-core (name/description come from the frontmatter, so they always match).
    • Referenced-source form.
    • Version history with a line diff (draft vs a published version, or version vs version).
    • Save draft; publish.
    • Rollout: pick a version, machines, and agents, then Preview plan (rollout-plan, per machine). Start rollout is enabled only after a successful preview for the same selection.
    • Assignment editor: assignments are SkillPreset desired-state resources in Fleet Git with no API write path. The editor emits the validated YAML to commit (scope all/group/tag/machine × agents, pinned catalogVersionId) rather than inventing a mutation.
  • Presets — per-machine Skills Manager presets from the snapshot. Links go to the machine tab for CRUD.
  • Search skills.sh — shown as a documented gap: the controller has no skills search operation, so it is shown with the fleetctl/CLI context rather than faked.
• Machine → Skills tab — library, presets, and per-agent deployments from GET /machines/{id}/skills.
  • Actions: install, update, check, deploy, undeploy, set-source, and the preset operations.
  • remove / adopt / preset-delete require a successful dry run of the same parameters before the real mutation is enabled.
• Conflicts — TARGET_CONFLICT and held_back_removals are parsed from operation errorJson/resultJson and shown as data (paths), with the ways out documented upstream in manage-skills: adopt or move aside for conflicts; for held-back removals, restore the paths in the source or resolve by hand. Nothing is auto-resolved.
• Every form shows "Copy as fleetctl".
• Tests: unit tests for the matrix/frontmatter/diff/YAML helpers, component tests for matrix states, and a page spec for edit→publish→preview→rollout against the stubbed API client.