Graffiti theme, outlined type, audit fixes, demographic copy - #3
Merged
Conversation
Nav links, buttons, and step labels now use -webkit-text-stroke to match the heading style: hollow/outlined letters in Vandal Blow font throughout. - .top-bar controls: Vandal Blow + text-stroke 1.5px - .btn primary: white fill, paper-stroke on ink bg - .btn.secondary: transparent fill, ink-stroke - .splash-step-label: Vandal Blow + text-stroke 1.5px Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DWWTyKs6t8zyYbVYavKSBn
The .splash-feature-card h3 override was setting solid color: var(--accent), cancelling the stroke. Now uses color: var(--paper) + text-stroke like all other headings. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DWWTyKs6t8zyYbVYavKSBn
Critical: - globals.css: add [data-theme="dark"] guard to reader-mode dark styles - rateLimit.ts: throw RateLimitError inside try block with explicit ROLLBACK, not after COMMIT outside the exception handler High: - friends.ts: listPublicFriends privacy check now allows page owner to see their own private-paged friends (viewerId === userId || viewerId === f.userId) - globals.css: remove 4 hardcoded border-radius: 2–4px values (→ 0) - guestbook.test.ts: 13 new tests covering sign/moderate/delete/count paths Medium: - globals.css: .btn.secondary text is now color: var(--ink) (was var(--paper) — invisible white text on transparent background) - pageDocument.ts: importPageData validates parsed value is a plain object before casting, not just truthy Low: - globals.css: .studio-pixel-clear uses var(--ink)/var(--accent-ink) instead of hardcoded rgba/hex - guestbook.ts: remove duplicate JSDoc comment on countPendingGuestbookEntries Tests: 194 passed (13 new) Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DWWTyKs6t8zyYbVYavKSBn
Rewrites all hero copy, feature cards, step labels, CTAs, and section headers for the 20-25 urban youth/artist demographic. Swaps corporate startup language for raw manifesto tone: "Claim your spot", "Tag it up", "Find your people", "Join the pool" — no feed, no algorithm, nothing sanitized.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThe PR revises platform copy and graffiti styling, expands dark-theme support, adjusts friend-page and import validation behavior, improves rate-limit transaction handling, and adds guestbook test coverage. ChangesPlatform messaging
Visual style updates
Access and input validation
Guestbook coverage
Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
zowskyy
marked this pull request as ready for review
August 21, 2026 15:39
zowskyy
pushed a commit
that referenced
this pull request
Aug 22, 2026
MAJOR Bug #4: Weak Test Assertions in proximityGraph.test.ts - Strengthened assertion 'falls back to random pages for null userId' Changed: expect(result.length).toBeGreaterThanOrEqual(0) → expect(result.length).toBeGreaterThan(0) Added: expect(result).toContain("wanderer") - Strengthened assertion 'returns only handles' Added: expect(result.length).toBeGreaterThan(0) before type check loop These were too weak to catch real bugs (empty array would pass) CRITICAL Bug #3 Verification: Ring Edge Provenance Loss - Added comprehensive regression test to webRings.test.ts - Test verifies weight-tracking system correctly preserves edges when users leave one of multiple shared rings - Scenario: user in 2 rings, leaves 1, edge persists with weight 1 - Result: Bug #3 is NOT actually a bug - weight system handles it correctly - But system is architecturally fragile, so regression test prevents future breakage Test Results: - All 251 tests passing (up from 235) - 19 test files, no failures - Regression tests protect against duplicate handle bug and edge loss scenario Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018V1rEEt5QTC2ww5ZikioWZ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--radius: 0px, black/white palette, no color except red for errors), dark mode wired correctly-webkit-text-stroke) — profile pages isolated so user themes are unaffected/logo.png); nav links in outlined Vandal Blow.msg-*thread layoutlistPublicFriendsprivate-page visibility logic,importPageDatatype validation, reader-mode dark guard for explicit[data-theme="dark"]toggleGenerated by Claude Code
Summary by CodeRabbit
New Features
Bug Fixes
Tests