Follow sluiceway v0.46.0: the command line talks to console.sluiceway.dev

[robbeverhelst]

The docs follow sluiceway v0.46.0. Step 0 saw pin=v0.45.0 latest=v0.46.0 open_prs=0. The release has one change (#285): the command line talks to https://console.sluiceway.dev. A token kept under the old app.sluiceway.dev still signs you in, and the next login keeps it under the new address. No page moves, no heading moves, and no picture, input, mode or schema key changes.

What it does

• The pin moves from v0.45.0 to v0.46.0: the submodule and the branch line of .gitmodules together (bun run pin: "vendor/sluiceway is at v0.46.0, and .gitmodules says so."). The build was green at the new pin with no mapping change. No check was weakened, and README_UNMAPPED is unchanged because the README has no new h2.
• The Command line page's examples print https://console.sluiceway.dev (src/lib/command-line.ts, 8 lines). Following docs: a Command line page for sluiceway v0.45.0, its commands, their --json answers and exit codes #23's method, I extracted the action at v0.46.0 and ran every one of the page's 18 example commands through its runCli against the fake app in test/cli/fake-app.ts. With the address swapped, all 18 match the page byte for byte, words and --json, with the same exit codes. So only the address changed.

Everything else arrives by itself: the command line page's new paragraph on the old address, the address in its Sign in, For agents and Where it connects sections, the glossary's App entry ("formerly app.sluiceway.dev"), and record 0116's new section "Amended, 2026-09-26". 0116 amends itself, so the records index derives no "Amended by" line from it.

Now wrong on the live site (fixed here)

The live site pins v0.45.0.

Where	Before (live)	After
Start page, JSON-LD	"Sluiceway v0.45.0", softwareVersion 0.45.0	v0.46.0 (both read the pin)
Command line, sluiceway login and --json	"Signed in to https://app.sluiceway.dev …", "app": "https://app.sluiceway.dev"	https://console.sluiceway.dev, as the command line at v0.46.0 prints
Command line, sluiceway status --json and sluiceway stack	the org and repo page fields on app.sluiceway.dev, and the deploy's status address	on console.sluiceway.dev
Command line, sluiceway logout and the not signed in failure	"Signed out of https://app.sluiceway.dev …", "Make a token on https://app.sluiceway.dev/settings/tokens …"	the new address

Checked and still right at v0.46.0: every description and title in pages.ts (none names an address), the hosted app pages, Get started and The app and the action (they already use console.sluiceway.dev since #24), the JSON-LD, the example dashboard (only its picture URLs and footer moved to the new tag, and the site serves pictures from the submodule), the header page and gallery, RECORD_PICTURES (0116 is not about Penny), and the anchor redirects (no heading moved). The command line page still shows app.sluiceway.dev twice, both in the action's own paragraph about the old address, which is right.

Different at the real tag from the plan

#23 and #25 left no plan, and #21's plan (#278, the layout keys) was released before v0.45.0. Nothing to compare.

When the open action PRs are released

sluiceway/sluiceway has no open pull request now. One thing is on its way, though:

• The app's live OpenAPI document is ahead of the action's copy. https://console.sluiceway.dev/api/v1/openapi.json (and the old address, which still answers) now adds a required unshared field ({ repos, sentence } or null) to Org and Audit, and the error code no-write-access. The action's test/fixtures/app/openapi.json at v0.46.0 has neither.
  • What breaks: when the action takes in this document, test/command-line.test.ts fails on sluiceway status infra --json, whose org has no unshared, and on any Audit answer on the page.
  • What to do: capture the examples again at that tag (runCli plus the fake app, as here), and consider an example of the no-write-access failure if the action's docs list it.

Ambiguous or wrong

In the action's own text at v0.46.0, for the coordinator to pass on. The release changed no record except 0116, and each older item was checked again at the tag.

• The README still does not link the Command line page. Record 0116 says "The README gains a link to it when the docs site has the page". The site has had it since docs: a Command line page for sluiceway v0.45.0, its commands, their --json answers and exit codes #23: https://docs.sluiceway.dev/hosted-app/command-line/.
• Records 0102, 0104, 0106, 0107 and 0109 still write no "Amended by" line on the records they amend. The index here derives them.
• Record 0095's seven amended records still do not say so.
• Record 0113's lead lacks a full stop before "Promise 4 of 0014 holds".
• Record 0047's lead has a date and no record: "Amended, 2026-09-22: …".
• Top-level cost in schema/sluiceway.schema.json has no description.
• recordWriters' description ends "Empty hands none on."
• action.yml's env-file wraps "relative to the" onto its own line.
• Record 0094 is "Amended by slice 5.32", which is a slice, not a record.
• docs/init.md still does not mention Terraform.
• workflow.md#the-workflow still points at the page title from 11 links.
• docs/roadmap.md still lists "a docs site" under the launch.
• Link text that is a file path in docs/using-the-dashboard.md: three [docs/…md] links.

How I verified

• DOCS_SITE=https://docs.sluiceway.dev DOCS_BASE=/ bun run check (lint, tokens, pin, release, astro check, build, tests) passes: 617 pass, 0 fail, 0 errors, 0 warnings, 0 hints. The build's only warning is the one main has too (the empty i18n collection). bun run release: "vendor/sluiceway pins v0.46.0, the action's latest release."

• Under both addresses, / and the default /docs, with the env set on each command: build, bun test (617 pass) and bun run links ("Checked 33011 links on 150 pages. All of them land.").

• The CLI capture: all 18 examples, run through runCli at v0.46.0 against fakeApp(), compared with EXAMPLES: the same output and exit codes once the address changes.

• Lighthouse, locally with bun run lighthouse (the repo's lighthouserc.json, production build under /, phone, median of three). All four scores are 90 or more on every audited URL:

  URL	Perf	A11y	Best practices	SEO	Weight (KB)
  /	99	100	100	100	154
  /get-started/	99	100	100	100	164
  /guides/configuration/	98	100	100	100	210
  /guides/notifications/	99	100	100	100	175
  /guides/policies/	99	100	100	100	171
  /guides/workflow/	99	100	100	100	180
  /reference/sluiceway-yaml/	99	100	100	100	172
  /reference/what-sluiceway-writes/	99	100	100	100	185
  /the-header/	99	100	100	100	201
  /using-the-dashboard/	99	100	100	100	171
  /what-it-looks-like/	99	96	100	100	170

  What it looks like scores 96 on accessibility for the same two <summary> folds under 44 pixels as at docs: follow sluiceway v0.42.1, a policies page and redirects for two renumbered records #20 and docs: follow sluiceway v0.42.2 #21.

• Screenshots: Playwright (global install), Chromium, 1280 and 390 wide, light and dark via prefers-color-scheme, each page scrolled to the end first so lazy pictures load, then checked for sideways scroll and broken pictures. The Command line page and record 0116, 8 full-page shots, with no sideways scroll and no broken picture. Then:

  • Sign in to the app (light, 1280): the Tokens address reads https://console.sluiceway.dev/settings/tokens, and the new paragraph about app.sluiceway.dev sits after the list of places a token is kept, every address in a code span.
  • sluiceway login (dark, 1280): "Signed in to https://console.sluiceway.dev as alice …", and the --json answer with "app": "https://console.sluiceway.dev". The long line scrolls inside its block, as before.
  • Record 0116, Amended, 2026-09-26 (dark, 390): the new h2 and its paragraph, the addresses wrapping inside the column.

Decisions no record covers

• The examples were captured again, not only searched and replaced. The release changed the token store too, and a capture is the only way to know that login and logout still print the same words.

Follow-ups

• Capture the command line examples again when the action's copy of the app's OpenAPI document gains unshared (above).
• The two <summary> folds of the example dashboard on What it looks like are under 44 pixels tall (Lighthouse, 96). A min-height on summary inside .sw-issue would fix it. Carried from docs: follow sluiceway v0.42.1, a policies page and redirects for two renumbered records #20.
• The action reference leaves a camelCase key without a dot as prose, such as "envFile" in the env-file description. Carried from docs: follow sluiceway v0.42.1, a policies page and redirects for two renumbered records #20.
• docs: a Command line page for sluiceway v0.45.0, its commands, their --json answers and exit codes #23's owner note still stands: What the app keeps says "The app keeps no token of yours, so it cannot act as you", while personal tokens let the command line act as the person. It needs a word from the app's side.

🤖 Generated with Claude Code