fix: keep Stack Scout launch validation current

[koltregaskes]

Summary

• narrow launch-safety private path detection to Kol/estate-specific paths
• keep service-worker cache name in sync when the site build refreshes the visible generated date
• refresh tracked generated output from the build without adding the local news-feed dump

Verification

• npm.cmd run build:site
• npm.cmd run check

Notes

• Supersedes fix: narrow launch-safety private path checks #8, which was closed because its branch picked up noisy generated-data history during repair.

[coderabbitai]

Warning

Review limit reached

@koltregaskes, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 42 minutes and 26 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7c6dc030-028e-4d5e-bf83-136e0f53a236

📥 Commits

Reviewing files that changed from the base of the PR and between 2ee5a39 and 4cafec9.

📒 Files selected for processing (38)

• catalog/index.html
• categories/apis/index.html
• categories/clis/index.html
• categories/desktop-apps/index.html
• categories/index.html
• categories/mcps/index.html
• categories/web-apps/index.html
• categories/web-services/index.html
• categories/websites/index.html
• collections/index.html
• data/categories-manifest.json
• data/collections-manifest.json
• data/methodology-manifest.json
• data/page-registry.json
• data/radar-manifest.json
• data/tools-manifest.json
• data/updates-manifest.json
• index.html
• method/index.html
• radar/index.html
• scripts/build-stackscout.js
• scripts/verify-launch-safety.js
• service-worker.js
• tools/anthropic-api/index.html
• tools/canvas-planner/index.html
• tools/gh-cli/index.html
• tools/github-mcp-server/index.html
• tools/hugging-face/index.html
• tools/make/index.html
• tools/n8n/index.html
• tools/openai-api/index.html
• tools/perplexity/index.html
• tools/playwright-mcp/index.html
• tools/signal-stack/index.html
• tools/strudel-studio/index.html
• tools/syncpad/index.html
• tools/wrangler/index.html
• updates/index.html

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/stackscout-launch-validation-clean

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6dfbee0b4c

ℹ️ 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 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 address that feedback".

[chatgpt-codex-connector]

Allow rerunning the site build on the same day

When service-worker.js already has today's cache name, current.replace(...) returns identical text and this branch throws even though the declaration is valid. I confirmed npm run build:site fails on June 6 with the checked-in CACHE_NAME = 'stackscout-2026-06-06', so any same-day rebuild or CI rerun after this commit is blocked by the new freshness sync.

Useful? React with 👍 / 👎.