docs/SUBMISSION.md

# Public Plugins Directory submission materials

These materials prepare a draft submission; they do not claim OpenAI review, approval, or publication.

## Listing

- Name: Context Handoff
- Category: Productivity
- Short description: Continue work in fresh threads
- Long description: Detect compaction with a trusted local lifecycle hook, then safely checkpoint and continue long-running Codex work in a fresh verified thread. Preserve language, acceptance criteria, evidence, workspace identity, and open risks. Preflight exact workspace compatibility to prevent approval loops, and verify a titled, pinned destination so handoffs remain discoverable from desktop and mobile.
- Developer: Tim Yu
- Website: https://github.com/timyeou1234/context-handoff
- Support: https://github.com/timyeou1234/context-handoff/blob/main/SUPPORT.md (enter in the portal; the supported plugin manifest schema has no support URL field)
- Privacy: https://github.com/timyeou1234/context-handoff/blob/main/PRIVACY.md
- Terms: https://github.com/timyeou1234/context-handoff/blob/main/TERMS.md
- Directory logo: `assets/logo.png` (512 × 512 PNG; current portal minimum is 256 × 256)
- Composer icon: `assets/icon.png` (256 × 256 PNG; current portal minimum is 48 × 48)
- Editable logo source: `assets/logo.svg`

## Starter prompts

1. Checkpoint this task and continue it in a fresh verified thread.
2. Prepare a safe handoff packet for this long-running Codex task.
3. Check context health and hand off only if a fresh thread is warranted.

## Release notes — 0.3.4

Makes fresh handoff destinations reliably discoverable in the Codex sidebar and on mobile Remote. The workflow assigns a concise `Handoff: <goal>` title, pins the exact returned thread, and verifies the same thread ID, host ID, and title in the pinned inventory before source archival. If that read-back fails, it reports `HANDOFF MOBILE VISIBILITY UNVERIFIED`, preserves the source, and returns the known destination identity. It also explains that local/worktree tasks require mobile Remote to connect to the same host. The 0.3.3 exact-workspace guard remains intact: incompatible routes never loop on elevated approval. No MCP server, hosted service, authentication, or reviewer credentials are used.

## USER-REQUIRED portal steps

GitHub Actions can build the versioned ZIP and checksum and can publish the matching GitHub Release. The OpenAI Platform submission remains a separate reviewed workflow; this repository has no submission credential or supported public submission API.

- Confirm Apps Management write access in the submitting OpenAI organization.
- Complete and select the correct verified individual or business identity.
- Review legal text and publisher identity with qualified counsel if required.
- Confirm the website, support, privacy, and terms URLs resolve publicly from the final release ref.
- Choose only countries or regions where support and legal terms are ready.
- Upload the final skill bundle and production logo, enter listing details and prompts, and add the reviewer cases from `docs/REVIEWER_TESTS.md`.
- Review and complete policy attestations personally.
- Submit for review only when authorized.
- After approval, choose whether and when to publish. Approval and publication are not established by this repository.