Add codex2api as a protocol-first OAuth source

This keeps the existing CPA, SUB2API, and contribution flows intact
while introducing codex2api as a separate source that plugs into
Step 7 and Step 10 through backend APIs instead of page DOM.

The sidepanel now exposes codex2api settings, preserves the built-in
local default through placeholder-only UI, and accepts user-provided
public admin URLs. Step 7 now treats missing or invalid management
secrets as terminal config errors so the flow stops instead of retrying
needlessly.

Constraint: New source must be additive and must not break existing CPA/SUB2API/contribution paths
Rejected: Drive codex2api through admin page button clicks | too brittle against frontend DOM changes
Rejected: Reuse contribution mode as a source surface | violates existing panelMode/runtime-mode boundary
Confidence: high
Scope-risk: moderate
Reversibility: clean
Directive: Keep codex2api on the protocol path unless its API becomes insufficient; do not add a panel content script without proving the protocol path cannot work
Tested: npm test; targeted codex2api/auth retry loops repeated 40 times; full suite repeated 5 times
Not-tested: Real browser run against a live codex2api instance with a real Admin Secret and OpenAI authorization

This commit is contained in:

initiatione

2026-04-22 13:57:21 +08:00

parent 27c8faa2a0

commit f8b919e883

21 changed files with 720 additions and 32 deletions

									
										sidepanel/sidepanel.css
									
		+11
		
												View File
												
				@@ -806,6 +806,17 @@ header {

				  flex-shrink: 0;

				}

				#row-codex2api-url .data-label,

				#row-codex2api-admin-key .data-label {

				  width: 76px;

				}

				#row-codex2api-url .data-label {

				  font-size: 10px;

				  letter-spacing: 0.02em;

				  text-transform: none;

				}

				.data-value {

				  font-size: 13px;

				  color: var(--text-muted);