Skip to content

Show campaign A/B results and weighted variations in CLI output - #76

Open
purpshell wants to merge 1 commit into
mainfrom
t3code/campaign-betas-output
Open

purpshell wants to merge 1 commit into
mainfrom
t3code/campaign-betas-output

Conversation

@purpshell

@purpshell purpshell commented Oct 11, 2026 •

Copy link
Copy Markdown
Member

Summary

Reconcile campaign A/B and weighted-variation human output on accepted CLI main 044f8b75ae8b0689664fe489c22d4a3c64486717. Published head: 7ad623a4876582aaa1cb80b92f87156c90105497, tree 449f1eaae905a1368d112025e03eb6eab1a1758b. The guarded rewrite replaces old afc9e016813211ee0af9b9d6e44421a966cfd2e3, preserving its author/date, helper and all 13 test cases.

The additive reconciliation preserves current follow-up, drip and frequency rendering, create flags/run body, agent setup and browser-shell changes. It adds escaped A/B outcomes and per-variant analytics, weighted counts, unknown-shape refusal and supported beta help. README guidance describes the existing update command correctly. JSON output and transport remain unchanged.

Exactly five source paths plus genuine contracts/cli-reference.json output change. Producer scripts, browser registry/policy, package manifest/lock and SDK pin remain byte-identical to 044f.

Impact

API behavior and feature policy are unchanged. Help claims were checked against accepted API eda77760b56095a771c55e5d2df18be23e985377. SDK source and package acceptance are separate; the CLI pin is unchanged. CLI human output/help and generated reference change here. Docs bundle adoption, registry publication, feature activation and environment acceptance remain held. Admin actions and controls are unchanged.

Verification

The completed local command, before this publication sweep, used a private copy of an existing lock-matching dependency graph with Node 24.15.0. No installer or shared donor write was used.

  • Unchanged 13 cases against compiled 044f: 4 controls pass, 9 expected missing-feature failures. Combined-source successor: all 13 pass with explicit OCLIF_TEST_ROOT.
  • Format, lint, typecheck, supported build, genuine reference generation/check/tests, browser registry generation, actual emitted-browser verifier and offline package dry-run pass.
  • Browser registry and support policy stay byte-identical to 044f; emitted assets are qualification artifacts only. No hardcoded command count or manual reference edit.
  • SDK pin and locked graph remain unchanged. Full suite, installed package/environment acceptance and hosted new-head CI are not claimed. Historical failures and resource receipts are retained. No broad tests, CI rerun or review was added for publication.

Fresh Git remote reads before guarded push still returned main 044f and expected old PR head afc9. A connector snapshot reported another base; it was not used to change source or claim a new integration.

Session provenance and UI evidence

Same Campaigns source owner, thread 646a0c0a-e900-4d0f-9a25-0b8834d7d4e6, Codex gpt-6.1-sol. Original campaign checkpoint: committed session evidence. The refreshed source/command/dependency/backup receipts are retained in the owner's publication packet. CLI fixture output only; no graphical UI or live provider acceptance.

Rollout and rollback

Keep draft. Release alone sequences merges. Revert the feature commit to remove the display/help additions; no state or schema changes. Matching published SDK/package and API environment evidence remain required for release. CLI72/79 stay held at their existing heads and pins. No registry publishing, feature activation, catalog date change or staging deployment.

@coderabbitai

coderabbitai Bot commented Oct 11, 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: a60f848f-369b-4d01-9d3c-7631b03fdcec
Commits

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

Files selected for processing: 6
  • README.md
  • contracts/cli-reference.json
  • src/commands/campaign/create.ts
  • src/services/campaign-experiments.ts
  • src/services/campaigns.ts
  • test/commands/campaign-experiments.test.ts
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

campaign analytics renders the A/B criterion, outcome, holdout and reserve
counts and a per-variant table with the winner marked. campaign view (and
create) show the variant count and outcome, and the number of weighted
message alternatives. campaign create help and the README describe the
variants, variantStrategy and messageVariations beta input fields.

The published SDK pin types these fields as unknown or omits them, so the
CLI narrows them at runtime with local types that accept the SDK main types
from polymorfa/sdks#344.
@purpshell
purpshell force-pushed the t3code/campaign-betas-output branch from afc9e01 to 7ad623a Compare October 28, 2026 23:43
@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:54.770742Z 7ad623a Draft marked ready
🔒 Security Review ✅ Completed 2026-10-31T04:48:31.110278Z 7ad623a 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