[#292] Layered page-thickness lines on book cards#293
Merged
realproject7 merged 1 commit intomainfrom Mar 18, 2026
Merged
Conversation
- Added 2 offset border layers behind the main card creating a stacked-pages / closed-book depth illusion - Page layers use decreasing opacity (border/40, border/60) - Thin top-edge line for page block thickness - Spine line on left preserved from #291 - All vector/stroke only, no fills or images Fixes #292 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
project7-interns
approved these changes
Mar 18, 2026
Collaborator
project7-interns
left a comment
project7-interns
left a comment
There was a problem hiding this comment.
T2b Review — APPROVED
Stacked-pages effect is well done:
- Two border layers at -5px/-3px offsets with 40%/60% opacity — good depth progression
- Wrapper margin (
ml-[6px] mb-[6px]) accounts for layer overflow within the grid cell pointer-events-noneon layers prevents click interference- Spine and top-edge line preserved
- Pure CSS, no JS, easy to revert
No issues found.
project7-interns
approved these changes
Mar 18, 2026
Collaborator
project7-interns
left a comment
project7-interns
left a comment
There was a problem hiding this comment.
Verdict: APPROVE
Summary
This is a contained follow-up to the book-card design: layered page-thickness lines and the thin top edge are added as vector/stroke elements while preserving content layout and the existing spine treatment.
Findings
- No blocking findings from this review pass.
Decision
Approving from my side. GitHub checks were still pending at the time of review.
3 tasks
realproject7
added a commit
that referenced
this pull request
Mar 27, 2026
Display full agent metadata (ID, name, description, model, genre, registration date, owner when different from bound wallet) in a new trust dashboard card for writer_type=1 profiles. Extends AgentMetadata interface with agentId and owner fields, fetched in parallel from the ERC-8004 registry. Non-agent profiles unaffected. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
realproject7
added a commit
that referenced
this pull request
Mar 27, 2026
Move URI resolution logic (raw JSON, data:, https://, ipfs://) into a shared resolveAgentURI() function in erc8004.ts. Used by both getAgentMetadata (server-side) and AgentManage (client-side) so agents registered via other apps with non-JSON URIs display correctly everywhere. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
border/40,border/60) for subtle depthTest plan
npm run typecheckpassesFixes #292
🤖 Generated with Claude Code