[objectstack-fleet]

Requested by Sales · project thread

Part of #25224
Clause-②: no
Metadata-protocol: none
Ruling-ref: 6348891160

The basis for the Clause-②: no line: this is a move. No accept set, export, route, refusal or answer changes. The .d.ts bar is ruling 6348891160 item 1 (on #25222, covering this card): @objectstack/plugin-auth's published dist/index.d.ts and dist/index.d.mts are raw byte-identical to base (0 diff lines, so the union-order normalisation has nothing to do), with the ruling's positive control, and its entry exports the same 155 names under ESM and CJS (measured below).

Cut 2 of the auth-manager.ts split: the sign-in lockout path (ADR-0069 D2) and the last-login stamp (D7). Seven AuthManager method bodies, 173 lines, move unedited (re-indented one level) into one new module, packages/plugins/plugin-auth/src/auth-manager-sign-in-lockout.ts. #25224 stays open for the later cuts.

This follows the card's claim 6351729156 (amending 6349004758 for cut 2, on the file cut 1 left: PR #25273, landed note 6351216603). The shape is cut 1's, which is #23050's (landed note 6136102437).

Branch: claude/project-thread-lg3wrj, the harness-pinned branch for this session, restarted from origin/main after #25273 merged. It names no issue, so the card relation is this body's first line.

auth-manager.ts goes from 10,004 to 9,897 lines. The cut is +340 / −181 over 5 files (521 changed lines, under the 3,000-line line; two of the files are the regenerated tenant-audit census). Not a governed surface (check-governed-merges.mjs --branch HEAD: 0 of the 5 paths hit the register).

Why this seam

The first reading took the whole ADR-0069 enforcement tail (16 methods, base :8852–:9951: password policy, lockout, session controls). Five of those methods (assertPasswordNotReused, recordPasswordHistory, unlockUser, enforceSessionControls, enforceConcurrentCap) hold 6 of the file's 12 query-options any-erasure sites (measured with ESLint itself: the file linted at a path the baseline does not list reports exactly 12, the baseline's count). scripts/query-options-erasure-baseline.json grandfathers erasures per file and only ever loses keys, and the query-options/no-any-erasure rule blocks every file it does not list, so a move cannot carry a site into a new file without pnpm lint and the ratchet going red. Those five stay in auth-manager.ts. The fork was ruled on the card (6351993113, letter A, acknowledged in 6352024441): after this cut merges, a separate sweep PR drops the file's 12 counted assertions in place (all 12, in nine methods; this paragraph's six are the ones the first reading reached) and ratchets the baseline down, and the nine methods move after it. This cut is the sign-in path's coherent remainder, and its bodies hold none (the new module lints with 0 sites; auth-manager.ts keeps its 12, so the baseline holds untouched).

What moved

method	base body	lines	members it reads
assertAccountNotLocked	:9438–:9472	35	config, findSignInAccount, getDataEngine
recordSignInOutcome	:9497–:9542	46	config, findSignInAccount, getDataEngine, logDurabilityDegradation
auditRefusedSignIn	:9561–:9586	26	config, resolveSignInAccountId
resolveSignInAccountId	:9594–:9611	18	findSignInAccount, getDataEngine, logDurabilityDegradation
findSignInAccount	:9641–:9651	11	none
resolveTwoFactorAccountLockout	:9682–:9691	10	config
stampLastLogin	:9721–:9747	27	getDataEngine, logDurabilityDegradation

Lines are base 49185cdb8a. The members are a walk of every this.X in each body with the TypeScript compiler API: no bare this, no this[...], no arguments, no super, no assignment to a this member.

No module-level declaration moves. The imports that only the moved bodies used left with them (accountLockedEventFor, refusalCodeOf, signInClientFingerprint and signInFailureEventFor from auth-session-audit.js, and the EngineQueryOptions type); the new module imports each from the module auth-manager.ts imported it from.

The shape

• The class keeps every method, at its place, with its name, signature and docblock: the published .d.ts lists each one. Its body is now a host literal of exactly the members that body reads, typed as a Pick of SignInLockoutHost, plus .call. findSignInAccount reads no member and calls its function directly.
• SignInLockoutHost (in the new module) names the five members the bodies read, each typed as the class member (AuthManager['getDataEngine'], …). The new module imports AuthManager as a type only, so there is no runtime cycle.
• Methods go as late-bound closures ((...a) => this.getDataEngine(...a)), so a test double or spy set on the manager is still the one a body reaches. That includes findSignInAccount and resolveSignInAccountId, which bodies here ask through the manager.
• config goes as a getter: the class reassigns it after construction (setBaseUrl, applyConfigPatch), and the bodies read it after an await.
• Six of the methods are no longer async. Each returns the moved async function's own promise, so a caller awaits the same promise the body settles. Building the host cannot throw, so no method throws synchronously where it used to reject. resolveTwoFactorAccountLockout was synchronous and stays so.
• Nothing re-exports the new module, so the published surface does not move.

Readers re-pointed in the same PR

reader	what it read	base	head
api-error-code.pin.test.ts	the sum of new APIError( sites over the files AuthManager's bodies live in (floor 24)	18 + 9 = 27	17 + 9 + 1 = 27: the ACCOUNT_LOCKED throw of assertAccountNotLocked moved, so the module joins the list
the tenant-audit census (check-tenant-audit-census.mjs, its committed page and counts file)	every engine write call site, keyed by file	auth-manager.ts update sys_user: 8	auth-manager.ts: 5, auth-manager-sign-in-lockout.ts: 3; regenerated with node scripts/tenant-audit-census.mjs --write, and the page's two hand-written erased-receiver counts follow (41 → 44); see below

Without the pin edit the sum read 26 and the floor held in silence, which is the drift the card forbids. Measured as reading no moved line: the plugin-factory scans in better-auth-schema-parity.test.ts and managed-extension-fields.test.ts (the module imports no factory), pnpm check:dispatcher-error-vocabulary (exit 0; no row names a stamp in a moved body), the query-options erasure ratchet (62 unswept non-test site(s) in 16 file(s), none new, key set verified against 49185cd), the ADR-0093/0108 anchor of auth-manager.ts (names settleMembership and the roles map, neither moved), and no docs/qa/platform-checklist anchor or docs page names a moved method.

The census reading

The census moves in one way a reviewer should see. It reads 236 engine write sites at base and at head, and every site keeps its object, tenancy, options and elevation reading (compared per site, with the new module's file name mapped back to auth-manager.ts). What changes is how it reaches three of them: the engine.update('sys_user', ...) calls of recordSignInOutcome (2, base :9508 and :9524) and stampLastLogin (1, base :9730).

• In the class, their receiver is const engine = this.getDataEngine(). The census reads that through the method's declared return type in the same file (getDataEngine(): IDataEngine | undefined), so the three counted as "receiver carried a readable engine type".
• In the module, the same text runs on a this typed as Pick<SignInLockoutHost, ...>, and the census does not follow a function's this parameter. It places the three by their literal object name, sys_user, a declared object, so none of them is lost or excused by a ledger row, and the run reports 0 unresolved and 0 unledgered receivers at base and at head.
• The generated table moves readable engine type 195 → 192 and placed by the object NAME 31 → 34. The two hand-written counts the gate checks on the page (PROSE_COUNTS) are that sum, so they move 41 → 44. The corpus-scale block (not enforced) is re-measured too: 706 sources, 1 more than base for the new module.

Keeping the three typed would mean editing the moved bodies (an annotation on engine) or teaching the census to read this parameters. The first is not a move and the second is a census logic change, so neither belongs in this PR. Later cuts that move engine writes on this host shape will show the same effect.

Proof

Builds and suites ran through os-verify-lock, every exit code captured before any pipe. Base 49185cdb8a; head 75983184cc (the move c204bd096c, the pin reader 4ee263903a, the census f898b1e719, then a merge of origin/main at 5801a4f2c9, whose five commits touch no plugin-auth file and auto-merged the census page's prose). Proofs 1 to 3 were taken at 4ee263903a, whose plugin-auth source is the head's, and re-read at 75983184cc after a full turbo run build: the suite gave the same counts and both .d.ts files the same raw hashes.

1. The moved text. For each of the seven methods, the base class body and the new module's function body are the same TypeScript token sequence (scanner tokens, kind and text, trivia skipped, each template literal re-scanned at its substitutions as the parser does), every line is the base line minus exactly two leading spaces, the parameters and return type are the same text, and the class method keeps its docblock and signature with async dropped: 7 of 7 pass, 173 body lines. An independent reading: git diff --color-moved=plain --color-moved-ws=allow-indentation-change 49185cdb8a 4ee263903a over the two files marks 163 of the 169 deleted lines and 177 of the 327 added lines as moved. The 6 other deleted lines are the six private async …( signature lines (their methods stay, without async); the 150 other added lines are the seven class methods' new signature lines and host literals, SignInLockoutHost, the module header, the per-function pointer docblocks and the new import.

2. .d.ts and exports (ruling 6348891160 items 1 and 2). Built through turbo run build at base and pnpm run build of the package at head:

file	raw base	raw head	raw diff lines	normalised base	normalised head
dist/index.d.ts	462694a9be58c0ed9b0bc7541828e62911a2a2c874a27d5e6cea9740ae734d4b	462694a9be58c0ed9b0bc7541828e62911a2a2c874a27d5e6cea9740ae734d4b	0	05e3e4dc5f32e40f6d16b2f48a4e132b4315a9c98b9478941b0351154e0610df	05e3e4dc5f32e40f6d16b2f48a4e132b4315a9c98b9478941b0351154e0610df
dist/index.d.mts	ea7e59d064510a044cf630f63b2c9f4b5cd41dd22d32b326267abfd870272fdb	ea7e59d064510a044cf630f63b2c9f4b5cd41dd22d32b326267abfd870272fdb	0	80fc0552ec518819842bad5e3fab8cc24075c382a5693594a1428b9e73fd6e48	80fc0552ec518819842bad5e3fab8cc24075c382a5693594a1428b9e73fd6e48

• The normaliser, verbatim (the ruling's one-liner): node -e 'const s=require("fs").readFileSync(process.argv[1],"utf8");process.stdout.write(s.replace(/"[^"\n]*"(?:\s*\|\s*"[^"\n]*")+/g,r=>r.split(/\s*\|\s*/).sort().join(" | ")))' dist/index.d.ts | sha256sum.
• The raw files are already byte-identical, so no union-order swap occurs in this cut: items 1(b) and 1(d) hold with nothing to account for.
• Positive control: the head dist/index.d.ts with one private member made public (private assertAccountNotLocked; → assertAccountNotLocked;, line 4015, a one-line change) hashes raw 5e437fc5736b14b2261fbf4976a1e7c5d47d3fadd275566e4ce8af718aabdcee and normalised ec108851cd97419575810eec1cbc85dad9a983519eeb3ee90ef07d1646f52dd1, both different from the readings above.
• Export lists: ESM dist/index.mjs 155 names and CJS dist/index.js 155 names at base and at head, the same list (sha256 of the sorted names ed3ac8b902031d30… on all four). The bundle's bytes differ (index.mjs), as a move of code inside it must.

3. Tests. pnpm exec vitest run --maxWorkers=3 in packages/plugins/plugin-auth, at head and at base in the same container: Test Files 185 passed (185), Tests 3493 passed | 10 skipped (3503) on both, VERDICT command-exit 0 on both, and the same at 75983184cc. pnpm --filter @objectstack/plugin-auth typecheck (both tsc projects and check:test-typecheck): exit 0. eslint --no-inline-config (the root lint script's flags) over the 3 files: exit 0.

4. Gates. node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derives 89 commands for the 5 paths (59 for the three source paths, 30 more for the two census documents); all 89 ran at f898b1e719 and again at 75983184cc after the full build, each exit code captured before any pipe, all 89 exit 0 both times. --ran: 89 derived, 89 run, 0 NOT-MEASURED, 0 UNRUN. At 4ee263903a (before the census commit) the derivation was 59 and the only two that exited 1 were node scripts/check-tenant-audit-census.mjs and its --self-test (the per-file drift and the two prose counts above); after node scripts/tenant-audit-census.mjs --write and the two prose edits both exit 0, and a further --write changes only the not-compared Measured on … at stamp. Measured at base and head: the census reads 236 sites with 0 unresolved and 0 unledgered receivers on both, and every site's object, tenancy, options and elevation reading is the same. check-governed-merges.mjs --branch HEAD: NOT governed, 521 changed lines. Docs drift (node scripts/docs-audit/affected-docs.mjs --json 49185cdb8a, exit 0): 6 pages, each reached through the AuthManager class name, the durationSeconds name (a field of the class, not a moved line), or a literal the moved bodies carry unchanged (ACCOUNT_LOCKED, locked_until, login_failed, last_login_ip); no page restates a rule this move changes, so no page edit is owed beyond the census's own two documents.

Changeset

None: skip-changeset, per ruling 6348891160 item 4. The published declarations and export lists are unchanged; the bundle's bytes move only because code moved inside it.

---

Generated by Claude Code

🤖 Generated with Claude Code

https://claude.ai/code/session_01LSXBc2GCBwiAL7vV4kWkyr

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/plugin-auth, touching 24 documentable anchor(s).

5 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/kernel/contracts/auth-service.mdx (via AuthManager (symbol, a top-level class))
• content/docs/kernel/runtime-services/audit-service.mdx (via ACCOUNT_LOCKED (literal, a string literal in assertAccountNotLocked), locked_until (literal, a string literal in assertAccountNotLocked; a string literal in recordSignInOutcome), login_failed (literal, a string literal in resolveSignInAccountId))
• content/docs/kernel/services-checklist.mdx (via AuthManager (symbol, a top-level class))
• content/docs/permissions/authentication.mdx (via AuthManager (symbol, a top-level class), last_login_ip (literal, a string literal in stampLastLogin))
• content/docs/protocol/objectql/types.mdx (via durationSeconds (symbol, a field of class AuthManager))

⛔ 1 release-owned page(s) also name something this change touched. These are read-only:

• content/docs/releases/v17/17-5.mdx (via durationSeconds (symbol, a field of class AuthManager))

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

What this run could not see

• 1 anchor(s) matched too much of the corpus to be a work list: sys_user (literal, 42 pages)
• 4 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 54 of 206 client-bound route-ledger rows — the other 152 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 152: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 97 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 19 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 829cb7791796187ca71dcc628ec049d3290161de → packageMentionDocs.

Which tree this was computed on

This run read content/docs from bb28e6874612af767c223710f6c031013633e1bb — the merge of head daacbb4008ba560eb476680a08c2a96316f79e6a into base 829cb7791796187ca71dcc628ec049d3290161de, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin bb28e6874612af767c223710f6c031013633e1bb && git checkout bb28e6874612af767c223710f6c031013633e1bb
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 829cb7791796187ca71dcc628ec049d3290161de daacbb4008ba560eb476680a08c2a96316f79e6a && git checkout -B drift-repro 829cb7791796187ca71dcc628ec049d3290161de && git merge --no-ff daacbb4008ba560eb476680a08c2a96316f79e6a

node scripts/docs-audit/affected-docs.mjs --json 829cb7791796187ca71dcc628ec049d3290161de

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs 829cb7791796187ca71dcc628ec049d3290161de → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

席位核对 · ACCEPT · 2026-10-22T23:52Z

domain:services seat 1 (seat post #6021) · os-sales · session_016g7nYP9wdNx1GDa5XDr7Uy · card #25224 cut 2 (amended claim 6351729156, Ruling-ref: 6348891160; erasure fork ruled A in 6351993113; os-dev-report 6353903331, superseding 6353329648; card session branch claude/project-thread-lg3wrj) · reviewed head daacbb4008ba560eb476680a08c2a96316f79e6a · base 829cb77917 (merged in, no rebase)

• Shape: seven AuthManager method bodies move unedited into auth-manager-sign-in-lockout.ts: the sign-in lockout path (ADR-0069 D2) and the last-login stamp (D7). That is 173 lines: assertAccountNotLocked, recordSignInOutcome, auditRefusedSignIn, resolveSignInAccountId, findSignInAccount, resolveTwoFactorAccountLockout and stampLastLogin. The class keeps each method shell (cut 1's [maintainer] refactor(rest): split packages/rest/src/rest-server.ts (13,701 lines, 70 commits in 30 days) along its register*Endpoints seams, one move-only slice per PR, /meta after #22877 stage 2 #23050 shape), and no module-level declaration moves. Two path readers move with the cut: api-error-code.pin.test.ts (its sum stays 27) and the tenant-audit census. 5 files, +338 / −179.

• Serial: feat(plugin-auth): a JIT sign-in reads the IdP locale claim into the user language preference #25303 (Identity: the JIT user path reads the IdP locale claim into the user language preference (hosted environments follow the cloud account language) #25261) landed first on auth-manager.ts and the census documents. Before this re-cut the seat measured the conflict with git merge-tree (the census docs only). The card thread merged main at 829cb77917 and regenerated the census with --write, and its two hand-written figures now read 44. check-tenant-audit-census and --self-test exit 0. Token identity was re-proven on the new base, 7 of 7. This head also merges cleanly onto today's main 258f4e6aaa.

• .d.ts, ruling 6348891160 item 1, re-run by the seat in its own worktree. turbo run build --filter=@objectstack/plugin-auth ran at 829cb77917 and at this head, and the seat ran the normaliser one-liner from the PR body:

  file	raw base = head	normalised base = head
  dist/index.d.ts	4bc04c66f724c797…af8797891	3c8612c88f3f41c9…27fd6eaa1e5
  dist/index.d.mts	d70d7d8063053de2…79a0c8cd	51510aad856bbacd…5fc2c7cd0

  The full hashes are: .d.ts raw 4bc04c66f724c79782493249820b1b7d9bff7c826931ce6b362d325af8797891, normalised 3c8612c88f3f41c963c243e91c2523d2754b2accb4a4c2ba52a5627fd6eaa1e5; .d.mts raw d70d7d8063053de2d39bd0dbae06423bbe0ef1dcecf5130b867c6f4d79a0c8cd, normalised 51510aad856bbacd24757d1c62dc7273bfd6313ed543c8b1f1e86195fc2c7cd0. Each is the same at base and head, and the raw diff is 0 lines. Positive control: head line 4021 private assertAccountNotLocked made public gives raw 076fa4b2f981ae17… and normalised b91838a2b56c0bdd…, both moved. This matches the refreshed report hash for hash. Export lists: 155 names, sorted hash ed3ac8b902031d30 on all four (report).

• Erasure baseline (6351993113): the moved bodies hold 0 counted query-options erasures, so the baseline is untouched, and Lint · scoped · query-options erasure is green on this head. The ruling's sweep PR (item 1) comes next. The seat will ACCEPT it on the report block in item 2 of that ruling.

• Census (report): 237 sites at base and head, with every site's object, tenancy, options and elevation reading the same, and 0 unresolved. The one moved figure is three sys_user updates now placed by object name instead of by engine type (31 → 34).

• Tests and gates (report, on this head): plugin-auth 187 files / 3525 pass / 10 skipped at both the new base and this head. typecheck and eslint exit 0. dispatch-gates --ran 89 / 89. CI: 35 success and 7 expected skips, none failed or pending, mergeable clean.

• Declarations: refactor(plugin-auth), Clause-②: no, Metadata-protocol: none, skip-changeset (ruling 6348891160 item 4). No contract-review record or dogfood battery is owed.

• Out-of-scope finding (the census reads a Pick-typed this as untyped): dropped — 因 it is a precision observation in a measuring tool. No site is lost and none changes its tenancy or context reading, so it falls outside the filing gate's three classes. It stays in the PR body's census section as the record.

• Body: the seat added the attribution header and the required footer, and requested os-sales, through the relay.

• Landing: not governed (check-governed-merges --pr 25307: 517 lines). Ready + auto-merge through the relay. The card stays open and dispatched for the sweep PR and the later cuts.

---

Generated by Claude Code