feat(landing): LANDING frame — white theme, editable hero, drops generator

[devclone20]

LANDING frame — rascunho de design

Primeira Landing pública do CLONE FRAME, a herdar a chrome de terminal dos frames.

Mudanças

• Tema branco por defeito (texto preto/cinza); toggle para dark mantido.
• Conceito iNFT simplificado — agente + NFT são um único token; removido o copy de marketing e a cadeia confusa "= chave = cofre".
• Imagem do herói editável — slot de upload (o utilizador escolhe a sua imagem).
• Drops — botão "Generate a drop" que desbloqueia o acesso aos tools da CLONE FRAME dentro da Venice (builtinvenice.ai).
• Staking 100k → 10k iCLONE (widget + README).
• Removido o link "What it is" da navegação.

Ficheiros

• frames/LANDING.widget (novo)
• README.md (staking 10k)

🤖 Generated with Claude Code

Greptile Summary

This PR introduces the first public LANDING frame for Clone Frame with a white default theme, an editable hero image slot, and a "Generate a drop" CTA that gates access to Venice tools. It also adds the full iCLONE FRAME mint-studio widget, updates the staking requirement from 100k to 10k iCLONE across README and the widget, and bundles SVG diagram assets for the FUTURES documentation section.

• LANDING.widget: new self-contained landing page with dark/light toggle, file-upload hero slot, smooth-scroll nav, and section cards for Frames and Economy. sendPrompt guard and innerHTML image-slot patterns flagged in prior review threads.
• iCLONE FRAME.widget: new mint-studio widget with collapsible sidebar, code-preview IDE (Solidity / deploy.ts / metadata.json tabs), mock wallet panel, and full Settings view. Contains unguarded sendPrompt calls in the Security/Danger-zone settings rows and user-controlled inputs injected directly into innerHTML in icMeta and icMint.
• README.md + docs/: staking threshold reduced to 10k, frame sequence renumbered, and new SVG FUTURES diagrams (Harness, Game Over, ACP Troubleshooter) added.

Confidence Score: 5/5

Safe to merge — the changes are design-prototype widgets with no backend, no persistent storage, and no production deployment path in this PR.

All changed files are self-contained UI mockup widgets and documentation. The JavaScript is client-side only with no data persistence, no API calls, and no cross-user surface. The two inline patterns flagged (unguarded sendPrompt in the Settings panel and user-input injected into innerHTML in icMeta/icMint) are limited to the widget's own transient DOM and do not cross trust boundaries in the current design-prototype context.

frames/iCLONE FRAME/iCLONE FRAME.widget — the icMeta and icMint functions should be hardened before any copy of this code is used in a context with persistence or shared state.

Important Files Changed

Filename	Overview
frames/LANDING.widget	New public landing frame with white theme, editable hero image slot, and sendPrompt-gated CTAs. Core layout and JS logic are sound; prior review already captured the sendPrompt guard and innerHTML image-slot concerns.
frames/iCLONE FRAME/iCLONE FRAME.widget	New mint-studio widget with sidebar nav, code-preview tabs, mock wallet, and Settings panel. Contains unguarded sendPrompt calls in Settings and user-controlled input injected directly into innerHTML in icMeta/icMint.
README.md	Staking threshold updated from 100k to 10k iCLONE; frame sequence and directory listing restructured. The numbered file listing in the README does not match the unnumbered filenames committed to frames/ (prior review).
frames/iCLONE FRAME/iNFT Configuration/BACKGROUND.widget	New background/layer configurator widget. Renders dynamic gallery and metadata via innerHTML; image src values come from FileReader data URLs (safe). State is entirely in-memory.
frames/iCLONE FRAME/iNFT Configuration/SILUETAS.widget	New silhouette/layer picker widget added as part of the iNFT Configuration sub-frame. Mostly static SVG layer selection UI with no notable logic issues.
docs/blueprint-construir.md	Documentation-only update to the build blueprint; no code changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([User opens LANDING.widget]) --> B{Theme toggle}
    B -->|cfTheme 0| C[White mode]
    B -->|cfTheme 1| D[Dark mode]
    A --> E[Click hero slot]
    E --> F[File picker opens]
    F --> G{File selected?}
    G -->|yes| H[FileReader.readAsDataURL]
    H --> I[cfImg: slot.innerHTML = img tag]
    G -->|no| E
    A --> J[Nav link: Frames / Economy]
    J --> K[cfGo: scrollIntoView smooth]
    A --> L[CTA: Generate a drop]
    L --> M{sendPrompt defined?}
    M -->|Venice host| N[Host handles prompt]
    M -->|standalone| O[ReferenceError thrown]
    A --> P[Frame card clicked]
    P --> M
    A --> Q[Footer: Venice link]
    Q --> M

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A([User opens LANDING.widget]) --> B{Theme toggle}
    B -->|cfTheme 0| C[White mode]
    B -->|cfTheme 1| D[Dark mode]
    A --> E[Click hero slot]
    E --> F[File picker opens]
    F --> G{File selected?}
    G -->|yes| H[FileReader.readAsDataURL]
    H --> I[cfImg: slot.innerHTML = img tag]
    G -->|no| E
    A --> J[Nav link: Frames / Economy]
    J --> K[cfGo: scrollIntoView smooth]
    A --> L[CTA: Generate a drop]
    L --> M{sendPrompt defined?}
    M -->|Venice host| N[Host handles prompt]
    M -->|standalone| O[ReferenceError thrown]
    A --> P[Frame card clicked]
    P --> M
    A --> Q[Footer: Venice link]
    Q --> M

Loading

_{Reviews (2): Last reviewed commit: "docs(futures): add GAME OVER arena + dar..." | Re-trigger Greptile}

[greptile-apps]

All interactive buttons call sendPrompt(...) directly, but sendPrompt is never declared inside the widget and has no guard. Outside the Venice/Claude host environment the first button press throws ReferenceError: sendPrompt is not defined, silently breaking all CTA and navigation links. A no-op fallback keeps the widget inert but non-crashing when previewed standalone.

Suggested change

	window.cfGo=function(s){
	var map={frames:'sec-frames',econ:'sec-econ'};
	var el=document.getElementById(map[s]);
	if(el) el.scrollIntoView({behavior:'smooth',block:'start'});
	};
	})();
	window.cfGo=function(s){
	var map={frames:'sec-frames',econ:'sec-econ'};
	var el=document.getElementById(map[s]);
	if(el) el.scrollIntoView({behavior:'smooth',block:'start'});
	};
	if(typeof sendPrompt==='undefined'){window.sendPrompt=function(){};}
	})();

[greptile-apps]

The image preview is built by concatenating the FileReader data URL directly into innerHTML. While readAsDataURL produces base64 output that cannot carry HTML metacharacters, creating DOM nodes via string concatenation is fragile as a pattern and will break if this function is ever extended to accept a URL (e.g. a remote image URL) that does contain quotes or angle brackets. Using document.createElement and setting src directly is safer and more explicit.

Suggested change

	r.onload=function(e){
	var s=document.getElementById('cfslot');
	s.classList.add('has');
	s.innerHTML='<img src="'+e.target.result+'"/><div class="slothint"><i class="ti ti-photo-edit" style="font-size:9px"></i> change image</div>';
	};
	r.onload=function(e){
	var s=document.getElementById('cfslot');
	s.classList.add('has');
	var img=document.createElement('img');
	img.src=e.target.result;
	var hint=document.createElement('div');
	hint.className='slothint';
	hint.innerHTML='<i class="ti ti-photo-edit" style="font-size:9px"></i> change image';
	s.innerHTML='';
	s.appendChild(img);
	s.appendChild(hint);
	};

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Naming convention mismatch between README and repo

The directory listing documents the canonical files as 1 - LANDING.widget, 2 - PLAZA FRAME.widget, etc., but the file actually committed in this PR is frames/LANDING.widget (no number prefix). Anyone following the README to sync from ~/Desktop/Widget Design/ will look for numbered files that don't exist in the repo, and contributors grepping the frames/ directory won't find the names listed here. Either rename the committed file to match the convention or update the listing to reflect the real names.