Add deterministic Community Metadata preview and download

[Caneryy]

Planning

• Plan ID: N2
• Depends on: Retire the duplicate community creation wizard #249 (H3)
• PRD alignment: FR-5; UJ-1

Problem

Creators must host a metadata JSON document before the wizard can validate it, but the app does not produce the canonical document they need to host.

Scope

Build a pure metadata serializer from wizard fields, show formatted JSON and its content hash on the review step, and add a client-side .json download. Do not upload or pin content.

Acceptance criteria

• The same normalized inputs always produce identical JSON bytes and hash.
• Preview and downloaded content match exactly.
• Required fields, URL schemes, and size limits are validated before download.
• Unit tests cover normalization, Unicode, escaping, and hash stability.

Verification

npm run lint && npm run typecheck && npm test

[s6pa1rta3n-lab]

/try

[naninu123]

Hi — I'd like to take #258 (deterministic Community Metadata preview and download).

Fit: TypeScript + deterministic serialization work. Scope is clear: pure serializer from wizard fields → canonical JSON bytes + content hash, formatted preview on review step, client-side .json
download. No upload/pin.
Plan:
1. Branch feat/community-metadata-preview
2. Map wizard field flow + review step → identify normalized input shape; note #249 (H3) dependency status and branch from current main, rebasing if H3 lands first
3. Implement serializer: stable key ordering + canonical escaping so identical normalized inputs yield identical bytes; compute content hash; render formatted JSON + hash on review step; .json
download matching preview byte-for-byte
4. Validate required fields, URL schemes, size limits before download; unit tests for normalization, Unicode, escaping, hash stability
5. npm run lint && npm run typecheck && npm test green → PR with proof + Closes #258

Can deliver inside the campaign window after assignment. Happy to join Discord/Telegram if needed.

[grantfox-oss]

🦊 GrantFox — @naninu123 has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #258)
2. Your PR will be reviewed by the stolla-labs maintainers

Good luck! Track your progress on GrantFox.