[scanner] PRs #132 and #143 collide on deploy-gh-pages.yml + validators-smoke.test.mjs — identical insertion points, guaranteed conflict #375

Finding

PR #132 (community staleness signal) and PR #143 (launch success metrics baseline) each insert a new validation step into .github/workflows/deploy-gh-pages.yml at the exact same location — hunk @@ -46,6 +46,9 @@:

• feat(community): add staleness signal for TAB/member profile currency #132 inserts Validate community profiles (npm run validate:community-people)
• feat(roadmap): define launch success metrics baseline + 90-day targets #143 inserts Validate launch metrics (npm run validate:launch-metrics)

Both PRs also append their new validator to READ_ONLY_VALIDATORS in tests/validators-smoke.test.mjs at the identical hunk @@ -15,6 +15,7 @@, and both touch package.json (which is now contested by 11 open PRs).

Because the insertion points are byte-identical, these PRs cannot both merge cleanly: whichever merges first puts the other into CONFLICTING state, requiring a manual rebase. Both PRs are already CONFLICTING with main today.

Evidence

PR #132: a/.github/workflows/deploy-gh-pages.yml @@ -46,6 +46,9 @@
         +      - name: Validate community profiles
         +        run: npm run validate:community-people
         a/tests/validators-smoke.test.mjs @@ -15,6 +15,7 @@ READ_ONLY_VALIDATORS

PR #143: a/.github/workflows/deploy-gh-pages.yml @@ -46,6 +46,9 @@
         +      - name: Validate launch metrics
         +        run: npm run validate:launch-metrics
         a/tests/validators-smoke.test.mjs @@ -15,6 +15,7 @@ READ_ONLY_VALIDATORS

Mergeable states as of 2026-09-21: #132 CONFLICTING, #143 CONFLICTING.

Recommendation

Sequence the merges deliberately: land one PR, then rebase the other and place the second validator step adjacent to the first (the validators are complementary, not duplicates — both should land). Add both new validator names to READ_ONLY_VALIDATORS in one follow-up rebase rather than racing. This is the same collision shape as #373 (CONTRIBUTING.md cluster) and is a symptom of the aggregate problem tracked in #58.

Filed by scanner agent (ACMM L4 — issues-only mode)

🐝 Hive Agent: scanner | Instance: hosted-available-lke648397-260827-5n31 | SHA: 00b44df

— hive: agent=scanner backend=copilot model=kimi-k3