Skip to content

docs(qa): re-point the two-factor-disable mfa_required anchor at a declaration the resolver reads - #21027

Merged
objectstack-fleet[bot] merged 1 commit into
mainfrom
claude/blissful-fermi-wci7b1
Oct 1, 2026
Merged

objectstack-fleet[bot] merged 1 commit into
mainfrom
claude/blissful-fermi-wci7b1

Conversation

@objectstack-fleet

Copy link
Copy Markdown
Contributor

Fixes #20464
Refs #20559
Clause-②: no

What this does

pnpm check:platform-checklist is red on main with one ABSENT SYMBOL: identity-auth.two-factor-disable-lifecycle cites packages/plugins/plugin-auth/src/auth-plugin.ts#twoFactor. Since the mfa_required forcing branch became a refusable patch, twoFactor survives in that file only as a key written INLINE in plugins: { twoFactor: true }, which the shared resolver deliberately does not read as a declaration.

The anchor now names mfa_required — the quoted settings key (isExplicit('mfa_required'), key: 'mfa_required') that guards the same forcing branch — and the parenthetical says why it moved. This is the same repair shape as the accept-set re-points: scripts/symbol-anchors.mjs is untouched, no citation is dropped to a bare one.

Premise check

The behaviour the item tests did not move: auth-plugin.ts still forces plugins.twoFactor on whenever mfa_required is explicitly on, so the card's "if the behaviour moved, report instead" branch does not apply. The item's steps, clauses and oracle are unchanged, so revision is not bumped (a citation re-point is not a semantic edit, as in the accept-set precedent).

Verification

  • symbolResolutionClass(auth-plugin.ts, 'mfa_required') → literal; 'twoFactor' → null (the red), measured at ef1ed17.
  • pnpm check:platform-checklist → OK — 15 areas, 268 items (264 active, 2 planned), symbol anchors 637/647 resolved … 10 on the named residual (unchanged residual).

Changeset

Docs-only (docs/qa/**): publishes nothing from any released package — skip-changeset.


Generated by Claude Code

…claration the resolver reads

`pnpm check:platform-checklist` was red on main with one ABSENT SYMBOL:
identity-auth.two-factor-disable-lifecycle cited
`auth-plugin.ts#twoFactor`. After the mfa_required forcing branch was
reworked into a refusable patch, `twoFactor` survives in that file only as
a key written INLINE in `plugins: { twoFactor: true }`, which the shared
resolver deliberately does not read as a declaration. The anchor now names
`'mfa_required'`, the quoted settings key that guards the same forcing
branch, and the parenthetical says why it moved. Same repair shape as the
accept-set re-points; scripts/symbol-anchors.mjs is untouched and the
item's steps, clauses and oracle are unchanged, so no revision bump.

Clause-②: no

Claude-Session: https://claude.ai/code/session_01MRdbfpy4sQT8bUjmMhxsN7
Co-authored-by: Claude <noreply@anthropic.com>
@objectstack-fleet

Copy link
Copy Markdown
Contributor Author

Landing note: this PR was authored in-session by the seat that later ran the P0 sweep, so the "a seat never lands its own PR" rule would normally hold it for a human merge. The maintainer authorized the landing explicitly: in Claude Code session session_01MRdbfpy4sQT8bUjmMhxsN7 on 2026-10-01 they selected the option verbatim 「授权我转 ready + 进队列(推荐)」.

Pre-landing check: the diff applied on main c27404f0 gives pnpm check:platform-checklist → OK — 15 areas, 269 items. CI on head ef1ed17f is 24 success / 11 skipped / 0 failed. The PR is flipped to ready and auto-merge is armed; the merge queue re-validates on the merged generation.


Generated by Claude Code

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

Labels

size/xs skip-changeset PR has no user-facing published change; bypasses the changeset gate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[finding] check:platform-checklist is red on main: identity-auth.json anchors auth-plugin.ts#twoFactor, which #20429 turned into an inline nested key

2 participants