fix(skills): shape template pins aesthetic v0.24.0

[moomooskycow]

Summary

• Re-pin the shape skill's html-plan.html template's aesthetic CSS link from @v2.5.1 to @v0.24.0.
• This is a forward-looking template that generates future planning artifacts, so it upgrades to the current kit version (not just a version-reset identity swap).

Context: fleet-wide aesthetic version reset 2.x → 0.x semantics (Powder landmark-017). Left .evidence/** and .harness-kit/traces/** archival plan outputs untouched — they're already-rendered HTML relying on the jsdelivr permanent cache, not templates.

Test plan

• Confirmed only the template file references the old pin; archival evidence HTML intentionally left alone
• CI green

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Single CDN version pin on a skill template with no runtime, auth, or data-path changes.

Overview
Re-pins the shape skill’s html-plan.html template so new planning artifacts load aesthetic from @v0.24.0 instead of @v2.5.1, aligning generated HTML with the fleet-wide 2.x → 0.x kit versioning (Powder landmark-017).

Only the forward-looking template changes; archived rendered HTML under .evidence/** and .harness-kit/traces/** is intentionally unchanged because those files rely on jsdelivr’s cached @v2.5.1 asset.

^{Reviewed by Cursor Bugbot for commit 5515840. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_156819bc-d3a4-490f-86ef-ec8c3aa4c186)

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5a497bfa-aad7-43a0-b4dc-b3c66a18ceec

📥 Commits

Reviewing files that changed from the base of the PR and between 826d373 and 5515840.

📒 Files selected for processing (1)

• skills/shape/templates/html-plan.html

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch aesthetic-v0-pin

---

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

[gemini-code-assist]

Code Review

This pull request downgrades the aesthetic.css stylesheet version from v2.5.1 to v0.24.0 in the html-plan.html template. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[github-actions]

🎉 This PR is included in version 1.19.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀