Skip to content

Docs catch up with 0.8.0 and the explore work - #88

Merged
addisdev merged 2 commits into
developfrom
docs/0.8-catchup
Oct 16, 2026
Merged

addisdev merged 2 commits into
developfrom
docs/0.8-catchup

Conversation

@addisdev

Copy link
Copy Markdown
Owner

Summary

Gaps these docs now admit, to be fixed in code later

  • The legacy POST /api/jobs/:id/cancel|retry have no owner check.
  • Legacy enqueue accepts shell from a run token.
  • ci-enqueue exits 0 on a skipped job and sends no token.
  • fleet/package.json bin points at a file the build does not produce.
  • The desktop version is not written by version.mjs.

Not in this PR

  • The three mermaid diagrams in the explore pages.
  • The 28-workload figure.
  • The dashboard screenshots, which predate the device drawings.

All of these need figures rendered, not text.

Test plan

  • mkdocs build --strict (Material 9.7.7) is clean.
  • fleet skill test passes (3/3) after npm run skill:gen.
  • check-bench.mjs fails a dump that still shows "Aloe Vera" and passes one that doesn't.
  • Not run: the full fleet and collector suites (no collector/node_modules in this worktree). The code changes are a comment, one generated string, and a standalone script.

🤖 Generated with Claude Code

addisdev and others added 2 commits October 15, 2026 20:16
bug-garden/tools/check-bench.mjs ignored the `absent_text` the harness
enforces, so bench-delete-plant passed without checking Aloe Vera was gone,
and it matched case-sensitively where the harness does not. It now does both
as the harness does.

The skill's exit-4 line said a skip meant "no build, no matching device".
Both of those are refused at enqueue (exit 2 or 5) and never run; exit 4 is a
job that was claimed and reported `skipped:`. Regenerated SKILL.md.

seed-schedules: the comment counted three explore schedules (there are four)
and still expected the TV one to wait for a Fire TV test; Fire TV is parked.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 0.8.0 changelog left out everything merged before the cut that was not
the control API: exploratory QA (#70, #73, #74, #77, #78), the device art
(#69) and the two runner-android fixes (#75, #76). They get an "Also in this
release" section with their not-verified items.

A read of every page against the code found ~60 stale spots. The main ones:

- Explore: card counts, Holo4's measured status, tool_choice and json_schema
  requirements, the real gateway-key lookup order and env vars, Fire TV
  parked for tvOS, the night-queue jobs and priorities, budgets, auth on
  POST /findings.
- Front door: Explore in the README, index and getting-started; 34
  workloads, not 28; "no authentication, by design" now says by default and
  links the opt-in tokens; the Roku driver; strict validation is /api/v1
  only; CI-verified items in platforms; ultra and the S8+ in the lab runbook;
  #45's caveat removed (fixed in 0.6.1).
- API and integration: undocumented routes and /metrics, the guards under
  FLEET_AUTH, CLI flags and env vars, the /api/v1-only owner and shell checks
  stated plainly. Guides lead with fleetr instead of the deprecated routes,
  say what ci-enqueue gets wrong (a skip exits 0; no token), add the
  required app.build to examples, and split an array "enqueue" no endpoint
  accepts into three specs.
- A tvloop section in workloads/host.md, which the catalog already linked.
- mkdocs nav listed the ultra runbook twice; it stays under Exploratory QA
  and the Deploy overview links it.

Not done here: the three mermaid diagrams in the explore pages, the 28-
workload figure and the pre-device-art dashboard screenshots. They need
figures rendered, not text edits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@addisdev

Copy link
Copy Markdown
Owner Author

Self-review: strict docs build and all 19 checks pass; code changes are a generated skill string, a comment and a standalone checker (tested against a dump). Merging per the plan (LOOP-PLAN Phase 0).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant