Skip to content

Own generation sessions and run artifacts in interfacectl - #31

Merged
mikeylong merged 5 commits into
mainfrom
codex/interfacectl-main-clean
Mar 13, 2026
Merged

mikeylong merged 5 commits into
mainfrom
codex/interfacectl-main-clean

Conversation

@mikeylong

Copy link
Copy Markdown
Collaborator

Summary

  • move generation session lifecycle and run artifact ownership into interfacectl
  • add canonical session/run schemas and CLI commands for init, record, summarize, and emit-run-artifact
  • update onboarding and generation docs to point at the canonical upstream workflow

Verification

  • pnpm --filter @surfaces/interfacectl-cli run test
  • GitHub commit status: success
  • Vercel deployment: completed

Notes

  • companion consumer cleanup: Surfaces-Platform/surfaces-webapps branch codex/surfaces-webapps-main-clean

@vercel

vercel Bot commented Mar 13, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
interfacectl Error Error Mar 13, 2026 5:46am

Request Review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8fdc82c946

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

const prohibitedRoles = uniqueStrings([...shellOwns, ...mustNotEmit]);

if (prohibitedRoles.length > 0) {
addRepair(repairs, "shell.primitive.disallowed", "high", "boundary", {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align shell-boundary repair code with adapter findings

buildRepairMapPayload emits the shell-boundary repair as shell.primitive.disallowed, but adapter outputs use shell-owned-primitive-emitted (including the guard output and validate remapping), and runSummarizeGenerationSessionCommand matches recurring findings to repairs by exact code. In repeated shell-boundary failures, this mismatch prevents recurringRepairCodes from surfacing the corresponding boundary repair instruction, so session summaries lose actionable guidance for a high-priority violation.

Useful? React with 👍 / 👎.

const loadedBundle = loadCompiledSurfaceBundle(options.bundleRoot, options.surfaceId, process.cwd());
const sessionId = options.sessionId?.trim() || buildDefaultSessionId();
const artifactsRoot = resolveWorkspaceRelative(workspaceRoot, options.artifactsRoot);
const sessionDir = path.join(artifactsRoot, options.surfaceId, sessionId);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Reject path separators in generation session IDs

The --session value is used verbatim in path.join(artifactsRoot, options.surfaceId, sessionId) without sanitization, so inputs like ../outside (or nested path segments) escape the intended artifacts/generation-sessions/... subtree. Because init-generation-session then creates directories, copies bundles, and writes JSON under that computed path, a crafted session ID can write artifacts outside the scoped session root and clobber unrelated files.

Useful? React with 👍 / 👎.

@mikeylong
mikeylong merged commit 2f3b946 into main Mar 13, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant