docs(auth): restate bootstrap-status as the bootstrap-window question, not "any user yet" (#14357)

[claude]

Fixes#14357

What changed

Two sentences in content/docs/permissions/authentication.mdx described bootstrap-status as answering "does this environment have any user yet?" — the pre-#14157 question. The handler doesn't answer that; it answers whether the admission gate's bootstrap window is open (no human user yet — service rows such as the legacy usr_system row don't count). This restates both sentences to match the handler, without touching anything else in the section.

Handler as the source of truth (packages/plugins/plugin-auth/src/auth-plugin.ts:2025):

returnc.json({hasOwner: !(awaitthis.authManager!.hasBootstrapWindow())});

hasBootstrapWindow() (auth-manager.ts:4148) resolves to isBootstrapCreation(), keyed on isHumanUserRow — a service row doesn't count as "has a user."

Before / after

### First-run bootstrap status (line 251)

• Before: "GET /api/v1/auth/bootstrap-status answers one question — does this environment have any user yet?"
• After: "GET /api/v1/auth/bootstrap-status answers one question — is the admission gate's bootstrap window open, i.e. does this environment have no human user yet? Service rows (such as the legacy usr_system row) do not count."

Endpoint index (line 1075)

• Before: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether this environment has any user yet"
• After: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether the admission gate's bootstrap window is still open — i.e. whether this environment has no human user yet"

Everything else in the section — public/unauthenticated by design, boolean-only response, the Console's /login vs /setup routing, and the fails-open behavior — is unchanged; it was already accurate.

Scope

Docs-only, no code touched. No changeset — this doesn't change any package's shipped behavior (skip-changeset label applied).

Gates

Derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/permissions/authentication.mdx — 30 families. Reconciled via --ran: 29 RAN-PASS, 1 NOT-MEASURED.

• RAN-PASS (29): check-ci-filter-parity, check-cross-package-test-inputs (node + pnpm), check-doc-frontmatter, check-doc-route-spelling, check-docs-section-name, check-section-landing-index, check-shard-attestation, check:doc-formula-expressions, check:doc-security-posture, @objectstack/spec check:docs, check:empty-state, check:liveness, check:skill-examples, check:strictness-ledger, check:variant-docs, check:yaml-examples, check:corpus-claim-drift, check:doc-anchors, check:doc-authoring, check:docs-audit-scope, check:docs-redirects, check:docs-single-h1, check:merge-driver, check:published-readme-links, check:react-page-adapter-contract, check:role-word, check:skill-identifier-liveness, check:vendor-version-stamps
• NOT-MEASURED (1): node scripts/check-test-completeness.mjs — needs a saved turbo run test log; CI tees it, local run with no argument exits 3 (PREREQUISITE NOT MET) by the gate's own design.

Head sha at gate time: 6e4304343.

---

Generated by Claude Code

[claude]

Fixes#14357

What changed

Two sentences in content/docs/permissions/authentication.mdx described bootstrap-status as answering "does this environment have any user yet?" — the pre-#14157 question. The handler doesn't answer that; it answers whether the admission gate's bootstrap window is open (no human user yet — service rows such as the legacy usr_system row don't count). This restates both sentences to match the handler, without touching anything else in the section.

Handler as the source of truth (packages/plugins/plugin-auth/src/auth-plugin.ts:2025):

returnc.json({hasOwner: !(awaitthis.authManager!.hasBootstrapWindow())});

hasBootstrapWindow() (auth-manager.ts:4148) resolves to isBootstrapCreation(), keyed on isHumanUserRow — a service row doesn't count as "has a user."

Before / after

### First-run bootstrap status (line 251)

• Before: "GET /api/v1/auth/bootstrap-status answers one question — does this environment have any user yet?"
• After: "GET /api/v1/auth/bootstrap-status answers one question — is the admission gate's bootstrap window open, i.e. does this environment have no human user yet? Service rows (such as the legacy usr_system row) do not count."

Endpoint index (line 1075)

• Before: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether this environment has any user yet"
• After: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether the admission gate's bootstrap window is still open — i.e. whether this environment has no human user yet"

Everything else in the section — public/unauthenticated by design, boolean-only response, the Console's /login vs /setup routing, and the fails-open behavior — is unchanged; it was already accurate.

Scope

Docs-only, no code touched. No changeset — this doesn't change any package's shipped behavior (skip-changeset label applied).

Gates

Derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/permissions/authentication.mdx — 30 families. Reconciled via --ran: 29 RAN-PASS, 1 NOT-MEASURED.

• RAN-PASS (29): check-ci-filter-parity, check-cross-package-test-inputs (node + pnpm), check-doc-frontmatter, check-doc-route-spelling, check-docs-section-name, check-section-landing-index, check-shard-attestation, check:doc-formula-expressions, check:doc-security-posture, @objectstack/spec check:docs, check:empty-state, check:liveness, check:skill-examples, check:strictness-ledger, check:variant-docs, check:yaml-examples, check:corpus-claim-drift, check:doc-anchors, check:doc-authoring, check:docs-audit-scope, check:docs-redirects, check:docs-single-h1, check:merge-driver, check:published-readme-links, check:react-page-adapter-contract, check:role-word, check:skill-identifier-liveness, check:vendor-version-stamps
• NOT-MEASURED (1): node scripts/check-test-completeness.mjs — needs a saved turbo run test log; CI tees it, local run with no argument exits 3 (PREREQUISITE NOT MET) by the gate's own design.

Head sha at gate time: 6e4304343.

---

Generated by Claude Code

[claude]

Fixes#14357

What changed

Two sentences in content/docs/permissions/authentication.mdx described bootstrap-status as answering "does this environment have any user yet?" — the pre-#14157 question. The handler doesn't answer that; it answers whether the admission gate's bootstrap window is open (no human user yet — service rows such as the legacy usr_system row don't count). This restates both sentences to match the handler, without touching anything else in the section.

Handler as the source of truth (packages/plugins/plugin-auth/src/auth-plugin.ts:2025):

returnc.json({hasOwner: !(awaitthis.authManager!.hasBootstrapWindow())});

hasBootstrapWindow() (auth-manager.ts:4148) resolves to isBootstrapCreation(), keyed on isHumanUserRow — a service row doesn't count as "has a user."

Before / after

### First-run bootstrap status (line 251)

• Before: "GET /api/v1/auth/bootstrap-status answers one question — does this environment have any user yet?"
• After: "GET /api/v1/auth/bootstrap-status answers one question — is the admission gate's bootstrap window open, i.e. does this environment have no human user yet? Service rows (such as the legacy usr_system row) do not count."

Endpoint index (line 1075)

• Before: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether this environment has any user yet"
• After: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether the admission gate's bootstrap window is still open — i.e. whether this environment has no human user yet"

Everything else in the section — public/unauthenticated by design, boolean-only response, the Console's /login vs /setup routing, and the fails-open behavior — is unchanged; it was already accurate.

Scope

Docs-only, no code touched. No changeset — this doesn't change any package's shipped behavior (skip-changeset label applied).

Gates

Derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/permissions/authentication.mdx — 30 families. Reconciled via --ran: 29 RAN-PASS, 1 NOT-MEASURED.

• RAN-PASS (29): check-ci-filter-parity, check-cross-package-test-inputs (node + pnpm), check-doc-frontmatter, check-doc-route-spelling, check-docs-section-name, check-section-landing-index, check-shard-attestation, check:doc-formula-expressions, check:doc-security-posture, @objectstack/spec check:docs, check:empty-state, check:liveness, check:skill-examples, check:strictness-ledger, check:variant-docs, check:yaml-examples, check:corpus-claim-drift, check:doc-anchors, check:doc-authoring, check:docs-audit-scope, check:docs-redirects, check:docs-single-h1, check:merge-driver, check:published-readme-links, check:react-page-adapter-contract, check:role-word, check:skill-identifier-liveness, check:vendor-version-stamps
• NOT-MEASURED (1): node scripts/check-test-completeness.mjs — needs a saved turbo run test log; CI tees it, local run with no argument exits 3 (PREREQUISITE NOT MET) by the gate's own design.

Head sha at gate time: 6e4304343.

---

Generated by Claude Code

[claude]

Fixes#14357

What changed

Two sentences in content/docs/permissions/authentication.mdx described bootstrap-status as answering "does this environment have any user yet?" — the pre-#14157 question. The handler doesn't answer that; it answers whether the admission gate's bootstrap window is open (no human user yet — service rows such as the legacy usr_system row don't count). This restates both sentences to match the handler, without touching anything else in the section.

Handler as the source of truth (packages/plugins/plugin-auth/src/auth-plugin.ts:2025):

returnc.json({hasOwner: !(awaitthis.authManager!.hasBootstrapWindow())});

hasBootstrapWindow() (auth-manager.ts:4148) resolves to isBootstrapCreation(), keyed on isHumanUserRow — a service row doesn't count as "has a user."

Before / after

### First-run bootstrap status (line 251)

• Before: "GET /api/v1/auth/bootstrap-status answers one question — does this environment have any user yet?"
• After: "GET /api/v1/auth/bootstrap-status answers one question — is the admission gate's bootstrap window open, i.e. does this environment have no human user yet? Service rows (such as the legacy usr_system row) do not count."

Endpoint index (line 1075)

• Before: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether this environment has any user yet"
• After: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether the admission gate's bootstrap window is still open — i.e. whether this environment has no human user yet"

Everything else in the section — public/unauthenticated by design, boolean-only response, the Console's /login vs /setup routing, and the fails-open behavior — is unchanged; it was already accurate.

Scope

Docs-only, no code touched. No changeset — this doesn't change any package's shipped behavior (skip-changeset label applied).

Gates

Derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/permissions/authentication.mdx — 30 families. Reconciled via --ran: 29 RAN-PASS, 1 NOT-MEASURED.

• RAN-PASS (29): check-ci-filter-parity, check-cross-package-test-inputs (node + pnpm), check-doc-frontmatter, check-doc-route-spelling, check-docs-section-name, check-section-landing-index, check-shard-attestation, check:doc-formula-expressions, check:doc-security-posture, @objectstack/spec check:docs, check:empty-state, check:liveness, check:skill-examples, check:strictness-ledger, check:variant-docs, check:yaml-examples, check:corpus-claim-drift, check:doc-anchors, check:doc-authoring, check:docs-audit-scope, check:docs-redirects, check:docs-single-h1, check:merge-driver, check:published-readme-links, check:react-page-adapter-contract, check:role-word, check:skill-identifier-liveness, check:vendor-version-stamps
• NOT-MEASURED (1): node scripts/check-test-completeness.mjs — needs a saved turbo run test log; CI tees it, local run with no argument exits 3 (PREREQUISITE NOT MET) by the gate's own design.

Head sha at gate time: 6e4304343.

---

Generated by Claude Code

[claude]

Fixes#14357

What changed

Two sentences in content/docs/permissions/authentication.mdx described bootstrap-status as answering "does this environment have any user yet?" — the pre-#14157 question. The handler doesn't answer that; it answers whether the admission gate's bootstrap window is open (no human user yet — service rows such as the legacy usr_system row don't count). This restates both sentences to match the handler, without touching anything else in the section.

Handler as the source of truth (packages/plugins/plugin-auth/src/auth-plugin.ts:2025):

returnc.json({hasOwner: !(awaitthis.authManager!.hasBootstrapWindow())});

hasBootstrapWindow() (auth-manager.ts:4148) resolves to isBootstrapCreation(), keyed on isHumanUserRow — a service row doesn't count as "has a user."

Before / after

### First-run bootstrap status (line 251)

• Before: "GET /api/v1/auth/bootstrap-status answers one question — does this environment have any user yet?"
• After: "GET /api/v1/auth/bootstrap-status answers one question — is the admission gate's bootstrap window open, i.e. does this environment have no human user yet? Service rows (such as the legacy usr_system row) do not count."

Endpoint index (line 1075)

• Before: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether this environment has any user yet"
• After: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether the admission gate's bootstrap window is still open — i.e. whether this environment has no human user yet"

Everything else in the section — public/unauthenticated by design, boolean-only response, the Console's /login vs /setup routing, and the fails-open behavior — is unchanged; it was already accurate.

Scope

Docs-only, no code touched. No changeset — this doesn't change any package's shipped behavior (skip-changeset label applied).

Gates

Derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/permissions/authentication.mdx — 30 families. Reconciled via --ran: 29 RAN-PASS, 1 NOT-MEASURED.

• RAN-PASS (29): check-ci-filter-parity, check-cross-package-test-inputs (node + pnpm), check-doc-frontmatter, check-doc-route-spelling, check-docs-section-name, check-section-landing-index, check-shard-attestation, check:doc-formula-expressions, check:doc-security-posture, @objectstack/spec check:docs, check:empty-state, check:liveness, check:skill-examples, check:strictness-ledger, check:variant-docs, check:yaml-examples, check:corpus-claim-drift, check:doc-anchors, check:doc-authoring, check:docs-audit-scope, check:docs-redirects, check:docs-single-h1, check:merge-driver, check:published-readme-links, check:react-page-adapter-contract, check:role-word, check:skill-identifier-liveness, check:vendor-version-stamps
• NOT-MEASURED (1): node scripts/check-test-completeness.mjs — needs a saved turbo run test log; CI tees it, local run with no argument exits 3 (PREREQUISITE NOT MET) by the gate's own design.

Head sha at gate time: 6e4304343.

---

Generated by Claude Code

[claude]

Fixes#14357

What changed

Two sentences in content/docs/permissions/authentication.mdx described bootstrap-status as answering "does this environment have any user yet?" — the pre-#14157 question. The handler doesn't answer that; it answers whether the admission gate's bootstrap window is open (no human user yet — service rows such as the legacy usr_system row don't count). This restates both sentences to match the handler, without touching anything else in the section.

Handler as the source of truth (packages/plugins/plugin-auth/src/auth-plugin.ts:2025):

returnc.json({hasOwner: !(awaitthis.authManager!.hasBootstrapWindow())});

hasBootstrapWindow() (auth-manager.ts:4148) resolves to isBootstrapCreation(), keyed on isHumanUserRow — a service row doesn't count as "has a user."

Before / after

### First-run bootstrap status (line 251)

• Before: "GET /api/v1/auth/bootstrap-status answers one question — does this environment have any user yet?"
• After: "GET /api/v1/auth/bootstrap-status answers one question — is the admission gate's bootstrap window open, i.e. does this environment have no human user yet? Service rows (such as the legacy usr_system row) do not count."

Endpoint index (line 1075)

• Before: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether this environment has any user yet"
• After: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether the admission gate's bootstrap window is still open — i.e. whether this environment has no human user yet"

Everything else in the section — public/unauthenticated by design, boolean-only response, the Console's /login vs /setup routing, and the fails-open behavior — is unchanged; it was already accurate.

Scope

Docs-only, no code touched. No changeset — this doesn't change any package's shipped behavior (skip-changeset label applied).

Gates

Derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/permissions/authentication.mdx — 30 families. Reconciled via --ran: 29 RAN-PASS, 1 NOT-MEASURED.

• RAN-PASS (29): check-ci-filter-parity, check-cross-package-test-inputs (node + pnpm), check-doc-frontmatter, check-doc-route-spelling, check-docs-section-name, check-section-landing-index, check-shard-attestation, check:doc-formula-expressions, check:doc-security-posture, @objectstack/spec check:docs, check:empty-state, check:liveness, check:skill-examples, check:strictness-ledger, check:variant-docs, check:yaml-examples, check:corpus-claim-drift, check:doc-anchors, check:doc-authoring, check:docs-audit-scope, check:docs-redirects, check:docs-single-h1, check:merge-driver, check:published-readme-links, check:react-page-adapter-contract, check:role-word, check:skill-identifier-liveness, check:vendor-version-stamps
• NOT-MEASURED (1): node scripts/check-test-completeness.mjs — needs a saved turbo run test log; CI tees it, local run with no argument exits 3 (PREREQUISITE NOT MET) by the gate's own design.

Head sha at gate time: 6e4304343.

---

Generated by Claude Code

[claude]

Fixes#14357

What changed

Two sentences in content/docs/permissions/authentication.mdx described bootstrap-status as answering "does this environment have any user yet?" — the pre-#14157 question. The handler doesn't answer that; it answers whether the admission gate's bootstrap window is open (no human user yet — service rows such as the legacy usr_system row don't count). This restates both sentences to match the handler, without touching anything else in the section.

Handler as the source of truth (packages/plugins/plugin-auth/src/auth-plugin.ts:2025):

returnc.json({hasOwner: !(awaitthis.authManager!.hasBootstrapWindow())});

hasBootstrapWindow() (auth-manager.ts:4148) resolves to isBootstrapCreation(), keyed on isHumanUserRow — a service row doesn't count as "has a user."

Before / after

### First-run bootstrap status (line 251)

• Before: "GET /api/v1/auth/bootstrap-status answers one question — does this environment have any user yet?"
• After: "GET /api/v1/auth/bootstrap-status answers one question — is the admission gate's bootstrap window open, i.e. does this environment have no human user yet? Service rows (such as the legacy usr_system row) do not count."

Endpoint index (line 1075)

• Before: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether this environment has any user yet"
• After: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether the admission gate's bootstrap window is still open — i.e. whether this environment has no human user yet"

Everything else in the section — public/unauthenticated by design, boolean-only response, the Console's /login vs /setup routing, and the fails-open behavior — is unchanged; it was already accurate.

Scope

Docs-only, no code touched. No changeset — this doesn't change any package's shipped behavior (skip-changeset label applied).

Gates

Derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/permissions/authentication.mdx — 30 families. Reconciled via --ran: 29 RAN-PASS, 1 NOT-MEASURED.

• RAN-PASS (29): check-ci-filter-parity, check-cross-package-test-inputs (node + pnpm), check-doc-frontmatter, check-doc-route-spelling, check-docs-section-name, check-section-landing-index, check-shard-attestation, check:doc-formula-expressions, check:doc-security-posture, @objectstack/spec check:docs, check:empty-state, check:liveness, check:skill-examples, check:strictness-ledger, check:variant-docs, check:yaml-examples, check:corpus-claim-drift, check:doc-anchors, check:doc-authoring, check:docs-audit-scope, check:docs-redirects, check:docs-single-h1, check:merge-driver, check:published-readme-links, check:react-page-adapter-contract, check:role-word, check:skill-identifier-liveness, check:vendor-version-stamps
• NOT-MEASURED (1): node scripts/check-test-completeness.mjs — needs a saved turbo run test log; CI tees it, local run with no argument exits 3 (PREREQUISITE NOT MET) by the gate's own design.

Head sha at gate time: 6e4304343.

---

Generated by Claude Code

[claude]

Fixes#14357

What changed

Two sentences in content/docs/permissions/authentication.mdx described bootstrap-status as answering "does this environment have any user yet?" — the pre-#14157 question. The handler doesn't answer that; it answers whether the admission gate's bootstrap window is open (no human user yet — service rows such as the legacy usr_system row don't count). This restates both sentences to match the handler, without touching anything else in the section.

Handler as the source of truth (packages/plugins/plugin-auth/src/auth-plugin.ts:2025):

returnc.json({hasOwner: !(awaitthis.authManager!.hasBootstrapWindow())});

hasBootstrapWindow() (auth-manager.ts:4148) resolves to isBootstrapCreation(), keyed on isHumanUserRow — a service row doesn't count as "has a user."

Before / after

### First-run bootstrap status (line 251)

• Before: "GET /api/v1/auth/bootstrap-status answers one question — does this environment have any user yet?"
• After: "GET /api/v1/auth/bootstrap-status answers one question — is the admission gate's bootstrap window open, i.e. does this environment have no human user yet? Service rows (such as the legacy usr_system row) do not count."

Endpoint index (line 1075)

• Before: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether this environment has any user yet"
• After: "Public, unauthenticated first-run probe: { "hasOwner": boolean }, telling a client whether the admission gate's bootstrap window is still open — i.e. whether this environment has no human user yet"

Everything else in the section — public/unauthenticated by design, boolean-only response, the Console's /login vs /setup routing, and the fails-open behavior — is unchanged; it was already accurate.

Scope

Docs-only, no code touched. No changeset — this doesn't change any package's shipped behavior (skip-changeset label applied).

Gates

Derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands content/docs/permissions/authentication.mdx — 30 families. Reconciled via --ran: 29 RAN-PASS, 1 NOT-MEASURED.

• RAN-PASS (29): check-ci-filter-parity, check-cross-package-test-inputs (node + pnpm), check-doc-frontmatter, check-doc-route-spelling, check-docs-section-name, check-section-landing-index, check-shard-attestation, check:doc-formula-expressions, check:doc-security-posture, @objectstack/spec check:docs, check:empty-state, check:liveness, check:skill-examples, check:strictness-ledger, check:variant-docs, check:yaml-examples, check:corpus-claim-drift, check:doc-anchors, check:doc-authoring, check:docs-audit-scope, check:docs-redirects, check:docs-single-h1, check:merge-driver, check:published-readme-links, check:react-page-adapter-contract, check:role-word, check:skill-identifier-liveness, check:vendor-version-stamps
• NOT-MEASURED (1): node scripts/check-test-completeness.mjs — needs a saved turbo run test log; CI tees it, local run with no argument exits 3 (PREREQUISITE NOT MET) by the gate's own design.

Head sha at gate time: 6e4304343.

---

Generated by Claude Code