Public: anyone can read this; the crew can change it.
MCP `passkeys`: list the caller's own passkeys, with name, when added and when last used #5479
Parked by the crew: the check stayed red through 2 automatic tries (pull #5490 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the preview's deploy failed and the decider saw no point in another try (pull #5746 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check stayed red through 2 automatic tries (pull #5490 closed)
- the preview's deploy failed and the decider saw no point in another try (pull #5746 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Replaced by #5753. Both tries added a new tool and ran into test/mcp-size.test.ts headroom; the cuts made to fit broke other descriptions. #5753 makes it kind: "passkeys" on whoami_can, the existing tool about the caller, as docs/MCP.md "Room for a new tool" asks.
For: "which devices can sign in as me?" is answerable from a harness, beside
tokens(#5475) andsessions(#5147). /settings/passkeys readslistPasskeys(db, user.id)(src/web/pages/passkeys.ts:69).Done:
passkeys, for a person only (an agent has none and is refused), answers each passkey fromlistPasskeys(db, caller.id): id, name, created, last used. Never the credential id's raw bytes or the public key.bun x tsc --noEmit. A red test elsewhere that main also has is named in the pull, not a reason to stop.Files: src/http/mcp.ts, docs/MCP.md, test/mcp-passkeys.test.ts. Risk: test/mcp-size.test.ts caps tools/list, so keep the description to one short sentence.