Date: 2026-09-13 UTC — V16 requirements Budget: USD 0 Candidate SHA: 9152f5a50de42be55508f0effed5ed09aee44c60 Status: PRE-SUBMISSION HANDOFF ONLY — DO NOT SUBMIT OR PUBLISH Current portal session: LOGIN_REQUIRED in the instrumented RumboNexus Brave profile; no cookie, localStorage, or credential extraction is permitted.

Before entering data, confirm in OpenAI Platform/Apps Management:

1. Sign in to the public plugin submission flow at https://platform.openai.com/plugins in the OpenAI Platform organization that owns RUMBO IA, and confirm the acting account has Apps Management: Write (organization owners already have it).
2. Confirm a verified individual or business identity exists in that same organization/project and matches the public RUMBO IA listing, website, support, privacy, and terms.
3. Confirm the selected OpenAI Platform project uses GLOBAL data residency. Current MCP review requirements state that EU-residency projects cannot submit MCP plugins for review.
4. Live support, privacy, and terms surfaces pass submission_gate.ts. Current Val Town surfaces are PASS and use the same candidate SHA.
5. The canonical RUMBO IA logo asset is hash-verified; portal upload remains unexecuted.
6. A production MCP URL/origin has been explicitly authorized. Do not submit the current URL merely because the staging adapter passes conformance.

Submission type: remote MCP-only / With MCP MCP URL mode: Universal Authentication: None Custom UI: None Reviewer credentials: Not applicable for bounded public v1

Use the exact listing and release-note fields from PORTAL_PACKET.json after its fail-closed fields have been resolved. Use exactly the three starter prompts in PORTAL_PACKET.json; do not add a fourth prompt. Use the current 5 positive and 3 negative reviewer cases from SUBMISSION_TESTS.md; they satisfy the current minimum requirement of at least 5 positive and 3 negative cases. A demo-recording URL is not a mandatory field in the current public submission or remote-MCP review documentation; do not block submission readiness on the historical DEMO_RECORDING_PLAN.md artifact.

When Apps Management supplies the exact domain challenge token:

1. Add it to the Val Town project as OPENAI_APPS_CHALLENGE_TOKEN using the secret/environment-variable mechanism; do not place it in source or chat logs.
2. Verify GET /.well-known/openai-apps-challenge returns HTTP 200 with only the exact token as plaintext.
3. Run verify.ts and submission_gate.ts again.
4. Do not continue if either fails.

Run Scan Tools in Apps Management against the authorized production MCP URL. Review every discovered tool and confirm the catalog contains exactly:

• crm_get_service_readiness
• crm_prepare_note
• crm_prepare_lead_stage_change
• crm_prepare_outreach_draft

For each discovered tool confirm:

• readOnlyHint=true
• openWorldHint=false
• destructiveHint=false
• schema matches the bounded contract
• no unplanned customer-data or mutating tool appears
• no unnecessary personal data, secret, debug field, or internal identifier is returned

If the scanned catalog differs, stop and reconcile source/host before continuing.

Select only countries/regions where the publisher, product, support and legal terms are actually ready. Do not infer worldwide availability from technical reachability.

Enter the starter prompts and release notes from PORTAL_PACKET.json and the reviewer test cases from SUBMISSION_TESTS.md.

Before pressing Submit for Review, return the portal evidence to the control plane and update these fields:

• APPS_MANAGEMENT_WRITE=PASS
• PUBLISHER_IDENTITY=PASS_VERIFIED_AND_MATCHED
• PROJECT_DATA_RESIDENCY=PASS_GLOBAL
• LOGO_ASSET=PASS
• LOGO_PORTAL_UPLOAD=PASS
• SUPPORT_MCP_SEMANTICS=PASS
• PRIVACY_MCP_DISCLOSURE=PASS
• TERMS_BOUNDED_SEMANTICS=PASS
• DOMAIN_VERIFICATION=PASS_COMPLETED
• SCAN_TOOLS=PASS_EXACT_FOUR_TOOLS_CURRENT_PRODUCTION_SNAPSHOT
• STARTER_PROMPTS=PASS_PACKET_CONSTRAINTS
• DISTRIBUTION_SCOPE=SET_EXPLICITLY
• POLICY_ATTESTATIONS=COMPLETED_AFTER_FINAL_REVIEW
• PRODUCTION_MCP_URL=AUTHORIZED_AND_PROVEN

Then rerun submission_gate.ts, verify_portal_packet.ts, validate_submission_import.ts, review_case_server_validation.ts, and verify_portal_evidence_v16.ts.

Only public_directory_state=READY_TO_SUBMIT with no technical or governance failures may establish technical submission readiness. It still does not grant authority to submit or publish.

SUBMISSION_GATE_PASS != SUBMISSION_AUTHORITY != REVIEW_APPROVAL != PUBLICATION_AUTHORITY