fix: harden StackScout launch validation#6
Conversation
Self-contained vanilla port of StackScout Prototype.html under prototype/ implementing Phase 1 of CLAUDE-HANDOFF-2026-05-zine.md: - 5-mood palette with localStorage persistence - Stack Scout wordmark + accent dot (two words, no issue number) - Cycling lead, sparklines, hover stripes, magnetic CTA, cursor spotlight - Film grain, marquee, live UTC clock, count-ups - Home rendered with placeholder data; Releases/Wire/List/Subscribe stubbed Adds DESIGN-2026-05-zine.md and CLAUDE-HANDOFF-2026-05-zine.md alongside the existing DESIGN.md so the new design spec is in-repo without overwriting the legacy spec. Live index.html is unchanged. Design pack source: W:\Websites\LOCAL-ONLY\stackscout\design-2026-05-19\ Source session: WEBSITE CODER (Linear KOL-533 family) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
stackscout.com is owned by an active server-monitoring company and stack-scout.com (the dashed alternative) is not Kol's preference. DNS check across 30 stack___.com candidates returned NXDOMAIN cleanly for stackgazette.com, which also matches the broadsheet/editorial mood already specified in DESIGN.md sec 1. Changes (prototype only — live site, repo slug, content/, scripts/ all untouched; see prototype/README.md for the cutover open items): - Wordmark: "Stack Scout" -> "Stack Gazette" - Logo mark: 10px accent square + glow ring -> three stacked horizontal bars (narrowest top, full-width middle, medium bottom) in the accent colour. Inline SVG, scales cleanly. - Hover: second word now swaps to accent colour - Title, meta description, canonical, theme-color updated - Crumbs across all stub pages updated - localStorage key renamed (stackscout.mood.v1 -> stackgazette.mood.v1) - Footer wordmark updated Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 35 minutes and 33 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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (47)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5df588aaa3
ℹ️ 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".
|
|
||
| ## Source design pack | ||
|
|
||
| Staged at `W:\Websites\LOCAL-ONLY\stackscout\design-2026-05-19\` (private). The `DESIGN-2026-05-zine.md` and `CLAUDE-HANDOFF-2026-05-zine.md` files at the repo root are copies of the design pack's authoritative spec and build plan, kept under the original "Stack Scout" name as a historical record of the round 03 design. |
There was a problem hiding this comment.
This file is committed under the public GitHub Pages repo, but this line exposes a machine-local W:\...\LOCAL-ONLY... private staging path and names the private design pack. That directly violates the repo guidance to keep machine-local paths and local-only/private ops data out of the public surface, and the new launch-safety scan won't catch it because prototype/ is not included in PUBLIC_ENTRIES; replace it with repo-relative/public instructions.
Useful? React with 👍 / 👎.
| - run: npm run build:site | ||
| - run: npm run check |
There was a problem hiding this comment.
On runs after 2026-06-04, this step rewrites index.html with that day's Issue date (build-stackscout.js stamps new Date()), and the immediately following npm run check runs the launch gate that rejects a service-worker cache date older than the generated issue date. Since service-worker.js is committed as stackscout-2026-06-04, every future PR/push validation will fail unless the cache name is manually bumped even when no content changed; avoid regenerating dated artifacts in validation or derive/update the cache date during the build.
Useful? React with 👍 / 👎.
|
Superseded by clean branch PR #7 after origin/main moved and the design branch became conflicting. |
1 participant
Summary
Verification