[purpshell]

Change

Add polymorfa session list, view, and status using the existing typed Platform SDK. An organization API key with sessions:read is required. list can filter by project; view and status use a team-unique session ID and reject --project before transport. status returns only stored status and optional reason, without claiming a live probe.

The API does not expose organization-key mint or rotate through this Platform surface, and the SDK has no typed methods for them. Existing key list/revoke, auth, project, and link commands are retained without invented credential mutations.

Public documentation is in monorepo PR #398, which must merge before this CLI PR.

Five-part assessment

• API: Unaffected for the read path. Existing org-scoped GET /platform/sessions and GET /platform/sessions/{id} require sessions:read. Organization-key mint/rotate remains blocked on a safe API contract and owner decision.
• SDKs: Unaffected for the read path. Exact dependency @polymorfa/sdk@0.1.0-dev.20260926005918 provides typed sessions.list/retrieve. Key mint/rotate is absent from its typed resource.
• CLI: Updated three read-only session commands, human/JSON output, scoped errors, and tests. Existing credential commands and exact SDK pin are unchanged.
• Docs: README updated here; public source-build guide updated in PR #398. No public changelog entry while the CLI npm package is unpublished.
• Feature release: Source-build only; no new API capability, flag, entitlement, experiment, deployment, or npm CLI publication. Live acceptance was not requested.

Verification

On Node 22: format, lint, typecheck, build, and full suite passed (916 tests, 4 skipped). New tests cover team/project list, view/status projection, credential authority, unsupported project filter, and missing-session failure.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[purpshell]

@codex review

[coderabbitai]

Warning

Review limit reached

• 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 11 minutes.

Check out review usage here.

View limit details

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

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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 656f902a-cc9f-447a-8d39-467ef30c1de6

📥 Commits

Reviewing files that changed from the base of the PR and between 374a01e and d196e1e.

📒 Files selected for processing (6)

• README.md
• src/commands/session/list.ts
• src/commands/session/status.ts
• src/commands/session/view.ts
• src/services/platform-management.ts
• test/commands/platform-management.test.ts

---

_{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-09-26T23:47:48.501909Z	d196e1e	Manual request

ℹ️ 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.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: d196e1e251

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".