Skip to content

[codex-goal-extension] emit goal lifecycle analytics - #27051

Closed
marksteinbrick-oai wants to merge 1 commit into
mainfrom
mark.steinbrick/rebuild-goal-analytics-extension
Closed

[codex-goal-extension] emit goal lifecycle analytics#27051
marksteinbrick-oai wants to merge 1 commit into
mainfrom
mark.steinbrick/rebuild-goal-analytics-extension

Conversation

@marksteinbrick-oai

@marksteinbrick-oai marksteinbrick-oai commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Emit the existing codex_goal_event contract from the canonical goal extension lifecycle after the extension migration.

- track created, usage_accounted, status_changed, and cleared events
- preserve turn attribution, cumulative accounting snapshots, and payload privacy
- return deleted goal rows so clear events retain the final goal ID and status
- cover extension, app-server, resume, budget-limit, and analytics serialization paths
@marksteinbrick-oai
marksteinbrick-oai deleted the mark.steinbrick/rebuild-goal-analytics-extension branch June 8, 2026 20:14

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

Copy link
Copy Markdown
Contributor

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: a2c01b4857

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".


[dependencies]
async-trait = { workspace = true }
codex-analytics = { workspace = true }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P2 Badge Update Bazel lockfile after dependency changes

This commit changes Rust dependencies in Cargo.toml/Cargo.lock, but MODULE.bazel.lock is not updated. That leaves CI’s Bazel lock validation at risk of failing, or Bazel builds using stale dependency metadata even though Cargo resolves locally.

Useful? React with 👍 / 👎.

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