Repository navigation
fix(tasks): bucket the title gateway flag per user - #127943
Conversation
|
😎 Merged successfully - details. |
|
@PostHog review --deep |
|
Risk: No findings This change buckets the Sentinel reviewed |
|
@charlesvien PostHog Review is reviewing this pull request. |
🤖 CI report
|
|
@PostHog stamp |
|
@charlesvien Stamphog is reviewing this pull request. |
There was a problem hiding this comment.
Approved.
The task write-path change has owning-team authorship and focused test coverage. No unresolved substantive concerns or other refusal grounds were found; the partial automated review does not count as independent review assurance.
- Author wrote 30% of the modified lines and has 41 merged PRs in these paths (familiarity MODERATE).
- PostHog Review (Deep) reviewed the current head (no findings) but skipped 2 changed files, so it does not count as assurance.
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 17L, 2F substantive, 47L/4F incl. docs/generated/snapshots — within ceiling |
| tier | ✓ | T1-agent / T1b-small (47L, 4F, single-area, fix) |
| stamphog 2.7.0 | .stamphog/policy.yml @ 63841cc · reviewed head 63841cc |

Problem
The
tasks-title-ai-gatewayflag was checked with a fixed distinct id, so any rollout percentage sent either every task title through the gateway or none (follow-up to #127830).Changes
create_taskpasses the creator's distinct id togenerate_task_titleand the flag buckets on it.task-title-generatorid.How did you test
New parametrized test for the flag distinct id, plus the title, facade and warm facade suites locally.