Skip to content

Add audience profile commands pending SDK prerelease - #79

Draft
purpshell wants to merge 5 commits into
mainfrom
t3code/audience-profiles
Draft

purpshell wants to merge 5 commits into
mainfrom
t3code/audience-profiles

Conversation

@purpshell

@purpshell purpshell commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

Summary

Refresh eight profile/consent/import commands against main 301bd6a and API dev 9bb1e2e. Gate --tag and --phone-prefix: help says "requires API support not yet available" and either flag fails before HTTP. The adapter sends only cursor/limit, so API #567 is required before enabling filters. No filtering claim.

SDK pin remains 0.1.0-dev.20261004024706; local types/authenticated raw transport bridge unpublished methods. Profile mutations disable retries. Includes the same MCP audit patch as #80.

Impact

Impact table

Area Status Evidence / blocker
CLI and README Updated Campaign commands, local HTTP fixtures and source examples in this PR.
CLI MCP dependency Updated Pin server/core 2.3.1 to fix the existing production audit failure; CLI stdio tool contracts stay unchanged.
SDKs Release blocked TypeScript registry pin stays 0.1.0-dev.20261004024706; local types/authenticated raw transport bridge missing methods. TS/Go/Python/PHP/C#/Rust package parity and acceptance remain separate SDK work (#348/#350/#351/#352).
Feature release / flags Release blocked Default-off betas, API deployment and matching package acceptance remain external gates. No availability or flag advanced.
Roadmap / transcript Blocked Coordinator owns Linear/Notion reconciliation and committed sanitized checkpoint; no synchronization claimed.

No impact table

Area Reason / evidence
API, libraries, runners/Bartender, Temporal, Logs/audit logs Client-only diff consumes dev 9bb1e2e; no routes, scopes, protocol, workflow or storage changes.
Admin API, controls/MCP, Inspector, Console and Admin UI No changed server or graphical UI paths; existing staff boundaries remain API-owned.
Onboarding, consent/tracking, billing/PAYG, Usage Existing authentication, consent input and server policy retained; no telemetry, prices, credits or meters added.
Server customer Analytics, Help Center and marketing Only existing analytics output is projected; no server calculations or launch copy changed.

Verification

Node 24: npm run verify passes (1,074 tests / 111 files, format, lint, typecheck, build, pack dry-run, zero production audit vulnerabilities). Three release-evidence tests and Actionlint pass. The 23 focused command tests cover all eight paths, pagination, CSV mapping/replay identity, revisions, API failures, unsupported-filter refusal with zero HTTP and four transient mutation failures sent once. Built help verifies both unavailable flag descriptions. API paths/scopes/fields/errors checked against dev 9bb1e2e; filters are absent there. No deployed API, import-worker execution, real send, hosted enrollment, registry install or publication exercised.

Session provenance and UI evidence

Parent thread 646a0c0a-e900-4d0f-9a25-0b8834d7d4e6; implementation agent gpt-6.1-sol through T3 Code. Sequential work, no requested automated reviews. Coordinator owns registration/checkpoint publication; that evidence is pending. Synthetic terminal/HTTP fixtures only; no GUI changes or screenshots.

Rollout and rollback

Leave draft; orchestrator merges. All PRs target main per RELEASING.md. Main push runs CI, not publication. publish-dev.yml runs at 02:30 UTC or manually and selects an exact registry SDK in disposable build inputs, requiring matching staging acceptance for nightly or production for stable. The existing contracts/abprops-capabilities.json has published: false, which independently blocks the publication gate. Merging source does not publish or prove availability. No workflow changes. Revert client changes before publication; published fixes need a new package. No migrations or flag changes.

Independent of #80/#81; README placement avoids their append conflict. Suggested order: #80, #81, #79. Keep filters gated until API #567 is merged, deployed and accepted; enabling them requires a separate verified change. SDK #350/#348 publication/acceptance remains external.

@coderabbitai

coderabbitai Bot commented Oct 16, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

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