Solana V2 devnet independent component evidence

Independent read-only Solana devnet component evidence for issue #902 at source 83827c0.

90 finalized receipt identities/statuses; two basic test-token assets (6 and 9 decimals), 24 receipts and 12 exact token movements. The extended 66 receipt statuses are not complete seven-scenario semantic acceptance. No devnet USDC, hosted API/keeper, owner reserve-release or mainnet activation claim.

Only safe public transaction references, amounts, digests and scoped results are included. No raw signed bytes, signing journal, private case data, source files, credentials or private trajectories are uploaded.

Payout consent before and after browser evidence

Before/after proof of the missing Payouts vault-consent control (PRD sections 3, 6, 7 and 11; PR #1275). Before: exact released c4ed318 artifact, expected missing-control failure. After: 28 targeted real-browser checks at 9769735 using deterministic API/wallet fixtures, passing all four viewports; source-file hashes bind the fixture revision to the committed changes. EVM and Solana co-signing, rejection, dialog focus and accessibility checked. Desktop and mobile screenshots visually reviewed. This is development evidence preceding the rebase to 504dd7c; it is not final-head full-suite or production acceptance. No native zoom, real user session, live wallet, mainnet action or provider readiness is claimed. Contains only selected screenshots/videos and safe proof metadata. No raw traces, source files, secrets, signed mainnet transactions or private journals.

PR 1302 referral recovery evidence at 6e7c2cff

PR 1302 referral claim recovery

Exact current source: 6e7c2cff9a0ea4f77800edf0a6e94e325e9b3964. Full repository verification and all 24 referral browser workflows passed on this source. Before media shows three counterexamples on unchanged development 2a85567e. After media uses the official frozen project fixture and synthetic wallet data; no real wallet or mainnet request is used.

The full 711-pass suite belongs to earlier 3eb26ba0 and is labeled separately. The rebased application and browser-test source is byte-identical; hosted final-head checks remain separate. Native 200% visual/keyboard completion remains pending. Media contains no raw trace, session, request log, private source, or signing data.

PR 1302 referral recovery browser evidence (3eb26ba0)

Referral claim recovery evidence

PR #1302. Source: 3eb26ba0b309c663c9ce160fe57135b847391fe8.

The before/ recordings and screenshots show three failed browser cases on development 2a85567e: blocked storage still permits a send; a refresh loses a known unverified claim after storage reads fail; a malformed marker permits another review without acknowledgement.

The after/ recordings cover all six workflows at 1440, 1024, 768 and 320 pixel widths: normal review and verified completion; disabled/stale/paused/unknown records; blocked writes; failed reads after submission; malformed-marker recovery; and an older finalized marker which must not confirm a newer claim. All 24 passed with zero skips, failures or retries. The normal review cases also retain keyboard, WCAG AA and strict console/network assertions. The screenshots are original browser captures; viewport captures can be scrolled, and named referral-review images show the full page.

The official fixture preparation supplies a frozen project registry. All 178 tracked application source files were compared with the PR source: only the generated registry and promotion projections differ. The claim component and all other application source are identical. Fixture Git metadata is retained separately from the application source identity. Synthetic API and wallet responses prove UI behavior, not live identity, token deployment, provider or financial acceptance. No real wallet key or chain was used.

Full source verification passed. The complete browser matrix and hosted checks are separate gates; this archive is the scoped recording result. Native Chrome keyboard/visual acceptance remains pending; no native screenshot or complete 200% zoom pass is claimed here.

Retained earlier attempts: the Vite development run rejected aborted StrictMode requests; a standalone production build omitted the project-registry fixture and its four normal-flow console checks failed on registry 404s. No assertion or application code was changed to hide those failures. The official fixture run in this archive passed.

Raw traces, request bodies, private paths, authentication/session data and source files are excluded. Each media file and safe receipt is hashed in MANIFEST.json.

PR #1300 first Solana vault evidence (ef5c39cd)

Controlled acceptance evidence for PR #1300, source ef5c39cd69e70e6340cefd89b7cfb43228710cde on development 2a85567e4eaa972d26f025f9457b6761fc8f3a2f.

The ZIP contains the before failure capture, eight after workflow videos and screenshots, accessibility and request assertions, local API startup logs, successful focused contract output, and source/served-asset hashes. Full local verification, the focused actual-validator owner flow, and all eight browser cases passed at this head. The earlier unfinalized test-mint failure remains identified in the receipts.

These are controlled local-validator and fixture-identity tests. The separate mainnet receipt is read-only program/Config verification. This evidence does not establish native 200% zoom, installed-wallet, deployment, mainnet funding, bounty award or payment acceptance. Current-head hosted checks remain separate. No production signing or activation occurred.

ZIP SHA-256: b725b915ce138112976864acbe71a1e91009626794b9d9d3ee944d6cf4a0d591.

PR #1300 final rebase evidence (950bd477)

Exact-head acceptance evidence for PR #1300, source 950bd4776bc46e09c685e870f9f81b630a2e9ee3 on development ebab2c427a396b87e8f4b08afe319784114dba64.

Full local verification and four real-handler/local-validator browser cases passed after the one-time rebase: ordinary and private-bounty owner setup on desktop and mobile. The archive includes unedited videos/screenshots, source and served-asset hashes, results and rebase equivalence. All repair source files remain unchanged by the rebase. The previous evidence stays immutable and retains its own source labels.

These are controlled local tests. No installed-wallet, native keyboard-only/200% zoom, deployment, mainnet funding or first-payment acceptance is claimed. No production signing or activation occurred. Hosted exact-head checks remain separate.

ZIP SHA-256: d01e14fe32f7ba6ddc6f2d2ce9660372f89f9b6a884760e2c2769167106a2f6c.

PR 1289 controlled UI evidence (ffc688c7)

Controlled UI evidence for PR #1289 at ffc688c71deb2b5078c2ad0fe1deaf2a49be84eb: eight desktop/mobile/tablet recordings, five screenshots, actual native Chrome 200% keyboard review/cancel evidence, and source/build/HTTP hashes. Synthetic API and wallet responses; no public-chain signing or live-payment acceptance. Original failure and evidence limits are documented in the package.

The later a2825502 build has identical compiled JavaScript, CSS and route HTML. This does not relabel the older test run as a final-head test.

Archive SHA-256: a0b917e78274768ca4e04d58439461e40d5aee8df53bb2cdcdaafc98b2db50b8. Captured evidence only; no production release or activation.

Solana pinned build reproduction at 208fbf5b

Read-only build evidence for PRD sections 6 and 11 and issue #901. A fresh pinned-image build at main source 208fbf5 reproduces the published edf3b34 candidate file and executable hashes. The program build succeeds; the overall command exits 1 only at the separately documented later host-IDL argument error. The JSON records this boundary. No second-machine verification, public-testnet acceptance, mainnet signing or activation is claimed. Program binaries, source files, credentials and raw logs are not uploaded in this packet.

Evidence: history reads preserve repository identity

Safe evidence for the immutable repository history repair at 2d467e3fb8d88ea05e015252c0aa5deab88ff372.

The bundle contains public HTTP metadata, actual staging and production registry identities, and summarized exact-source HTTP/SQLite workflow results. It contains no credentials, private source captures, prompts, model responses or raw test logs.

This proves history transport and predecessor preservation. It does not prove model quality, deployment or historical scoring completion. The existing historical publication hold remains in place.

Historical Points publication hold evidence — 82ceeb6e

Safe exact-source evidence for historical Points publication hold at 82ceeb6e8f2d65286d896fd0652b2a20695d74f0. Includes real local importer/SQLite/Points HTTP workflow results, source mapping and full verification. No raw source captures, prompts, responses, credentials or private traces. No deployment, score publication or payment.