Skip to content

Clarify dual-lane macOS E2E policy#121

Open
Farhan (fkb032) wants to merge 1 commit intodevelopfrom
fkb/e2e-dual-lane-pivot
Open

Clarify dual-lane macOS E2E policy#121
Farhan (fkb032) wants to merge 1 commit intodevelopfrom
fkb/e2e-dual-lane-pivot

Conversation

@fkb032
Copy link
Copy Markdown
Contributor

Summary

  • Defines the dual-lane macOS E2E policy: Computer Use remains the broad PR Product Proof lane; Peekaboo AX/screen-capture is complementary Mac proof.
  • Updates Peekaboo report/workflow copy from Computer Use parity claims to Computer Use correspondence.
  • Changes Peekaboo CI/report semantics so incomplete Computer Use correspondence is visible in the report but no longer fails the complementary Peekaboo lane by itself.
  • Adds guardrails against teammate-specific driver terminology in generated report checks and removes existing person-specific wording from repo/report surfaces.

What changed operationally

  • peekaboo-e2e.yml no longer downgrades an otherwise passing Peekaboo run to inconclusive solely because cu_covered != cu_required.
  • The final Peekaboo result job no longer exits non-zero solely for incomplete Computer Use correspondence.
  • run-local.mjs no longer downgrades Peekaboo single/suite reports to inconclusive solely for missing Computer Use keys; self-tests now assert that missing breadth is reported as correspondence while failed Peekaboo-owned evidence still fails.

Hygiene

  • .beads runtime state is intentionally not included.
  • No Scott/scott teammate-specific terminology remains in tracked code/docs/report surfaces.
  • No native-driver wording was introduced; the lane is described as Peekaboo AX/screen-capture or shell/AX where mechanism matters.

Verification

  • git diff --check
  • node --check tools/computer-use-e2e/run-local.mjs
  • node --check tools/computer-use-e2e/workflow-contract-self-test.mjs
  • node --check tools/computer-use-e2e/peekaboo-workflow-contract-self-test.mjs
  • node tools/computer-use-e2e/workflow-contract-self-test.mjs
  • node tools/computer-use-e2e/peekaboo-workflow-contract-self-test.mjs
  • node tools/computer-use-e2e/run-local.mjs self-test
  • node tools/computer-use-e2e/run-remote-cua.mjs self-test
  • Repo scan for Scott/scott returned no matches.
  • Repo scan for rejected native-driver terminology returned no matches.

Claude review was run before execution; the blocking feedback was to avoid framing this as docs-only because CI/report behavior changed. This PR uses e2e: framing and calls the gate change out explicitly.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 8, 2026

Fails
🚫

PR description is missing a ## Test Plan (or ## Testing Instructions) section. Add one describing how a reviewer can verify your change, or tag the PR #trivial if no testing is needed.

🚫

This PR touches behavior-sensitive code that is documented in darkmatter/nixmac-web. Please either:

  • Open a companion docs PR and check Docs updated in the PR description, or
  • Check No docs update needed if the change doesn't affect user-facing behavior.
Warnings
⚠️ Please assign this PR to someone (usually yourself).
Messages
📖

🤖 This PR touches CI / infra — reviewers please pay extra attention:

  • .github/workflows/peekaboo-e2e.yml

📋 PR Overview

Lines changed 224 (+171 / -53)
Files 1 added, 10 modified, 0 deleted
Draft / WIP no
Has Test Plan no
New UI components no
New Storybook stories no
New Rust modules no
New TS source files no
New tests no
package.json touched no
Cargo.toml touched no
Infra / CI touched yes

Generated by 🚫 dangerJS against fe77812

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fe77812bf6

ℹ️ 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 (@codex) review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".

['visual report callouts', !hasScreenshots || /data-visual-annotation="report-callouts"/i.test(html)],
['raw screenshot fallback', !hasScreenshots || /Open raw screenshot/i.test(html)],
['peekaboo ax overlay labeled', !hasPeekabooAxOverlays || /Peekaboo AX overlay/i.test(html)],
['no teammate-specific driver terminology', !TEAMMATE_SPECIFIC_DRIVER_PATTERN.test(html)],
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Narrow teammate term scan to generated copy

When a PR title or head ref contains Scott (for example a branch like fkb/scott-peekaboo-local-e2e), the workflow forwards that metadata into the Peekaboo report and renderPeekabooPrFocus renders it in the HTML before verify-report runs. This new whole-document regex therefore fails the report for user-supplied PR metadata even though the generated driver terminology is clean, blocking an otherwise passing Peekaboo lane; the check should exclude dynamic PR metadata or scan only the report copy it owns.

Useful? React with 👍 / 👎.

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