fix(self-driving): keep the session replay scout eligible for capture cliffs - #413
Draft
posthog[bot] wants to merge 1 commit into
Draft
posthog[bot] wants to merge 1 commit into
posthog[bot] wants to merge 1 commit into
Conversation
… cliffs Replay Vision scanners read only recordings that exist, so they cannot detect a capture cliff. Split session replay in the route map: scanners own on-screen defects, signals-scout-session-replay owns recording capture. Step 6 now treats the scout as a specialist candidate, and step 6b never proposes a custom scout for recording capture. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Generated-By: PostHog Desktop Task-Id: 4d0e1f04-2c64-45ab-a7f2-3f702fc0b78c
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a wizard branch:
Add Results will be posted here when complete. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
signals-scout-session-replay, so a project that uses Session Replay loses its only capture-integrity watcher.Origin
Changes
The route map splits session replay into two seams:
signals-scout-session-replayStep 6: only the error-tracking scout stays routed elsewhere. The session-replay scout is a normal specialist candidate when step 2 found recordings. If step 6 disables it, the follow-up says what it watches.
Step 6b: recording capture is never a custom-scout surface. If the built-in scout is off, setup records a note to enable it, not a custom copy. A rerun keeps this division.
Step 6c: says the scanners cannot see a capture cliff, and that step 6 owns the scout.
Note
The session-replay scout now competes for one of the at most five specialist slots. It does not add a slot or raise the ten-scout ceiling.
Test plan
npm testpasses.npm run buildpasses. The new text is indist/skills/self-driving-setup.zip.Agent context
signals-scout-session-replaybody to confirm that capture integrity is its first job.Created with PostHog Desktop from this inbox report.
🤖 Generated with Claude Code