[purpshell]

Remove key list, key revoke and project-token list because organization keys and project tokens cannot manage long-lived credentials. A signed-in person manages them in the Console. Remove the commands, topic discovery, service helpers, examples and docs; preserve local credential profiles and all client-token behavior.

Six-part impact:

• API updated in companion monorepo PR (linked below), source cdc3d8dd2770693f1d319ecf5d0fa1a058717a0d: remove the three public credential-management routes; retain human Console/account routes.
• SDK updated in companion SDK PR (linked below), deleting corresponding resources/types/exports. This CLI uses no replacement SDK method, so its existing registry dependency remains valid; a package release is not fabricated.
• CLI updated: commands, service functions, help topics, tests and examples removed together. Unknown-command tests prove no transport occurs.
• Docs updated: README and research/design amendment here; Mintlify and dated changelog in monorepo.
• Feature release updated in the monorepo record; no flag, entitlement, enrollment, pricing or environment change. Source changes do not prove registry availability.
• Admin unaffected: staff admin-api-keys v1 and its named Temporal functions remain.

Validation: npm run typecheck, npm run build, npm run lint pass. 60 affected command/context/forwarding tests pass on Node 24.15.0, including removal of each command before transport. The broader initial suite passed 1073 tests with one loopback TLS test failure on Node 26; that test passes on Node 24. Tests/coverage gates are unchanged except replacing superseded command expectations with command-absence tests.

Delivery remains coordinated with the monorepo/SDK removal. No publish, deployed API acceptance or authenticated Console browser session was exercised. SDK publication has a separately reported missing GitHub App client-id/private-key gate; no workaround is included. This PR targets dev as requested; main remains the repository default publication branch.

Companion delivery: https://github.com/polymorfa/polymorfa/pull/641 · polymorfa/sdks#354 · #83

[coderabbitai]

Warning

Review limit reached

The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.

• Ask an admin to enable usage-based reviews

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Next included review available in 1 minute.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available. Your 67 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Team
• Run ID: fc96fffa-96d6-403f-81c0-12e201f5cf50

📥 Commits

Reviewing files that changed from the base of the PR and between add5500 and d394f2b.

📒 Files selected for processing: 10

• README.md
• docs/command-research/platform-management.md
• docs/superpowers/specs/2026-08-19-polymorfa-cli-design.md
• package.json
• src/commands/key/list.ts
• src/commands/key/revoke.ts
• src/commands/project-token/list.ts
• src/services/platform-management.ts
• test/commands/platform-management.test.ts
• test/commands/project-context.test.ts

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-17T18:20:17.076926Z	d394f2b	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-17T18:20:57.167176Z	d394f2b	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.