Skip to content

docs(qa): 18.0 sweep round 10 — the walled boot's release attribution, two comma-range citations, the console-dist fact re-measured #24788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
objectstack-fleet merged 3 commits into from
Oct 20, 2026
Merged

docs(qa): 18.0 sweep round 10 — the walled boot's release attribution, two comma-range citations, the console-dist fact re-measured #24788

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9a85df9
qa(checklist): the walled boot's release attribution, and two comma-r…
claude Oct 20, 2026
8bfefd5
Merge remote-tracking branch 'origin/main' into claude/issue-24579-v1…
claude Oct 20, 2026
13865e5
qa(checklist): fill the round's history refs with the PR number
claude Oct 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/qa/platform-checklist/RUNNER.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -458,7 +458,12 @@ contradicts it, and correct it here when it does.

- **A walled boot is a fixture of its own: `os serve` boots `group` and `isolated` once the
walled prerequisites are provisioned, and the stock showcase provisions none of them.**
18.0 refused a walled posture at boot; 18.x step 4 (#24580) removed that refusal, so
18.0.0 boots a walled posture: under ruling record 6282882793 on the v18 epic it is
published only after 18.x step 4 (#24580) has merged, and step 4 deleted the boot refusal
(`walledPostureRefusal()` in `packages/cli/src/commands/serve.ts`). Of the builds published
so far, only the `18.0.0-next.5` prerelease carries that refusal, as `main` did from
`ae6bd1a6` until step 4: `next.0` to `next.3` predate it, and no `next.4` was published.
So on 18.0.0
`OS_TENANCY_POSTURE=group` or `isolated` (or the legacy `OS_MULTI_ORG_ENABLED=true`, which
`resolveTenancyPosture()` in `packages/types/src/env.ts` reads as `isolated`) boots through
`os serve`, and so `os dev` and `os start`. Each prerequisite below refuses the boot with a
Expand Down
Loading
Loading