Ensure the boundary artifact prep script actually runs under Node, treat agent-harness declarations as required freshness markers, and narrow the codex approval bridge to the dedicated approval-runtime SDK surface.
Regeneration-Prompt: |
Latest origin/main already contains most of the earlier main CI type fixes, so first compare the branch against origin/main and drop anything already landed upstream. Keep the final branch scoped to the remaining root-cause fix: the plugin SDK boundary artifact prep command was using import.meta.main, which is undefined under the Node runtime here, so the standalone command could silently no-op even when required declaration outputs like agent-harness.d.ts were missing. Update that entrypoint guard to use process.argv[1] with pathToFileURL, add agent-harness declaration outputs to the freshness sets for both root and package artifacts, and keep the codex approval bridge importing ExecApprovalDecision from the narrower public approval-runtime subpath. Verify with the standalone boundary-artifact command and scoped linting, and note that full pnpm check on latest origin/main is currently red because of an unrelated no-unnecessary-type-assertion failure in src/auto-reply/reply/strip-inbound-meta.ts.
fcf4e1112c