[#502] Profile page — writer stats and story portfolio

[realproject7]

Summary

• Added writer stats section: total storylines, total plots, total donations received, claimable royalties (own profile only via connected wallet)
• Enhanced per-story metrics: title, plot count, token price, holder count (from trade_history), view count, genre, active/complete status, creation date
• AI agent extras: average plots per story, genre distribution tags, model info from ERC-8004 agentURI
• Improved empty state for addresses with no stories
• Holder count derived from trade_history net position (mints - burns > 0)

Test plan

• Visit a writer profile — verify stats section shows storyline count, total plots, donations
• Visit own profile (connected wallet) — verify claimable royalties appear
• Visit another writer's profile — verify claimable royalties field not shown
• Verify per-story rows show token price, holder count, genre, status
• Visit an AI agent profile — verify Agent Insights section with avg plots/story, genre tags, model
• Visit an address with no stories — verify empty state message

Fixes #502

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
plotlink	Ignored		Mar 24, 2026 7:14pm

[project7-interns]

Verdict: REQUEST CHANGES

Summary

The story portfolio work is close, but the writer stats section still misses a required aggregate holder metric, and the per-story holder count logic is incorrect for multi-token trades.

Findings

• [high] The writer stats block does not show the required total token holders aggregate. On other people's profiles it renders Holders: —, and on your own profile it replaces the holder stat entirely with Claimable. Issue #502 requires both total token holders and claimable royalties when viewing your own profile.

  • File: src/app/profile/[address]/page.tsx:323
  • Suggestion: Compute and render aggregate holder count across the writer's stories, and keep claimable royalties as an additional stat instead of replacing holders.

• [high] Per-story holder count is computed from event count, not token amount, so it produces false zero/non-zero balances whenever a user mints or burns multiple tokens in one trade. The trade indexer stores only event_type, not the minted/burned amount in trade_history, so mint => +1 / burn => -1 is not a valid holder balance reconstruction.

  • File: src/app/profile/[address]/page.tsx:403
  • File: src/app/api/cron/trade-history/route.ts:172
  • Suggestion: Derive holder counts from actual token balances or persist trade amounts needed for balance reconstruction; do not ship holder counts based on raw event tallies.

Decision

Requesting changes because the current implementation still misses a required top-level stat and can show materially incorrect holder counts in the story portfolio.

[project7-interns]

Verdict: REQUEST CHANGES

Summary

The top-level holder stat is now present and claimable royalties are shown as an additional stat, but the core holder-counting bug is still unresolved. Both the aggregate holder count and the per-story holder count are still derived from raw mint/burn event tallies rather than token amounts.

Findings

• [high] Holder counts are still materially incorrect for multi-token trades. The new aggregate totalHolders query and the per-story holderCount query both do mint => +1 / burn => -1, but the trade indexer only persists event_type to trade_history even though the source events include amountMinted / amountBurned. A user who mints 10 tokens and later burns 1 token will be treated the same as someone who minted 1 and burned 1.
  • File: src/app/profile/[address]/page.tsx:252
  • File: src/app/profile/[address]/page.tsx:405
  • File: src/app/api/cron/trade-history/route.ts:172
  • Suggestion: Persist the traded token amount needed for balance reconstruction, or derive holder counts from actual token balances instead of event counts.

Decision

Requesting changes because the PR still displays holder counts that can be wrong in normal multi-token trading flows.

[project7-interns]

Verdict: REQUEST CHANGES

Summary

The invalid holder-count reconstruction is gone, but the PR now substitutes token supply where issue #502 explicitly requires token holders. That means both the top-level writer stat and the per-story metric still do not match the ticket.

Findings

• [high] The PR replaced the required holder metrics with token supply. Issue #502 calls for total token holders across all stories and per-story holder count, but the current implementation now renders Token Supply from the latest trade_history.total_supply instead. Token supply is a different metric and does not satisfy the acceptance criteria.
  • File: src/app/profile/[address]/page.tsx:251
  • File: src/app/profile/[address]/page.tsx:327
  • File: src/app/profile/[address]/page.tsx:407
  • Suggestion: Restore holder-focused metrics by deriving actual holder counts from a reliable source, rather than swapping the UI to token supply.

Decision

Requesting changes because the current implementation still does not deliver the holder metrics required by issue #502.

[project7-interns]

Verdict: APPROVE

Summary

The holder metrics now match issue #502 again. The writer stats section includes the required aggregate numbers, and both the aggregate holder stat and per-story holder count are derived from on-chain balanceOf checks rather than placeholder or event-count approximations.

Findings

• None.

Decision

Approve because the stories tab now provides the required writer stats, per-story metrics, AI agent extras, and empty state in line with issue #502.