Skip to content

test(channels): preserve newsletter metadata in CLI output - #92

Open
purpshell wants to merge 5 commits into
mainfrom
codex/pol81-newsletter-observations
Open

purpshell wants to merge 5 commits into
mainfrom
codex/pol81-newsletter-observations

Conversation

@purpshell

@purpshell purpshell commented Oct 27, 2026 •

Copy link
Copy Markdown
Member

Summary

Preserve optional newsletter observations, reported zeroes and empty maps in existing event/channel JSON and NDJSON output. No new command or SDK release pin.

Current main 044f8b75ae8b0689664fe489c22d4a3c64486717 is merged into c18bc473df810eedb10ce741e8a41fdd193566f5, retaining accepted browser/agent functionality. Exact runtime dependencies and resolved lock packages are preserved; Zod remains4.6.7 and the SDK pin remains0.1.0-dev.20261004024706. No installer ran.

Verification and readiness

Not review-ready yet. Source/dependency containment and merge ancestry were inspected. The bounded serialized claim exited75 before CLAIMED, so current-head build, native browser producers, CLI-reference producer check and focused tests did not run locally. Natural new-head CI is separate; older ec49f19 CI is historical. No assertion was weakened.

Source only. Publication, matching API acceptance and Release-owned merge gates remain. No package/tag release or deployment.

@coderabbitai

coderabbitai Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.

  • Ask an admin to enable usage-based reviews

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Next included review available in 11 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available. Your 56 included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour.

Learn how review limits work.

Review configuration:

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Team
  • Run ID: ddfed614-e2df-480f-9f79-f9978fb903e2
Commits

Reviewing files that changed from the base of the PR and between 044f8b7 and c18bc47.

Files selected for processing: 5
  • README.md
  • contracts/newsletter-observations.json
  • test/commands/newsletter-observations.test.ts
  • test/fixtures/newsletter-observations/channel-message.json
  • test/fixtures/newsletter-observations/delivery.json
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@purpshell
purpshell force-pushed the codex/pol81-newsletter-observations branch from b15dafa to ec49f19 Compare October 28, 2026 03:42
@purpshell
purpshell marked this pull request as ready for review October 31, 2026 04:46
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-31T04:47:49.942989Z c18bc47 Draft marked ready
🔒 Security Review ✅ Completed 2026-10-31T04:48:04.630688Z c18bc47 Draft marked ready
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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