fix: migrate all quasar examples to current Quasar API (PR #195 + #196)

[mikemaccana-edwardbot]

Quasar landed two breaking changes on 2026-05-03 (HEAD 3d6fb0d8):

• PR Add basics/favorites/poseidon solana-developers/program-examples#195 (blueshift-gg/quasar#195) — derive plugin extensibility. Replaced the namespaced mint::* / token::* syntax with behaviour-style mint(...) / token(...), renamed program markers (Token → TokenProgram, System → SystemProgram), replaced inline seeds = [...], bump with address = T::seeds(...) driven by #[derive(Seeds)], replaced init_if_needed with init(idempotent), and renamed DynCpiCall to CpiDynamic. String instruction args now require an explicit capacity bound (String<N>).
• PR Add basic/realloc/poseidon solana-developers/program-examples#196 (blueshift-gg/quasar#196) — extracted Metaplex Token Metadata into its own quasar-metadata crate. The MetadataProgram marker moved out of quasar-spl::metadata::*.

Together these broke every quasar example in the repo. This PR migrates them to the current API (44 commits, one per example).

What's in the PR

Group	Examples	Status
basics/*	14	All green (account-data, checking-accounts, close-account, counter, create-account, cross-program-invocation/{hand,lever}, favorites, pda-rent-payer, processing-instructions, program-derived-addresses, realloc, rent, repository-layout, transfer-sol); hello-solana built clean as-is
tokens/*	9	All green (create-token, escrow, external-delegate-token-master, nft-minter, nft-operations, pda-mint-authority, spl-token-minter, token-fundraiser, token-swap, transfer-tokens)
tokens/token-extensions/*	8	basics and cpi-guard built clean as-is; default-account-state, immutable-owner, interest-bearing, memo-transfer, mint-close-authority, non-transferable, permanent-delegate, transfer-fee migrated. group stays ignored ("not live"); metadata is an empty placeholder dir.
tokens/token-extensions/transfer-hook/*	7	All green
compression/*	3	All green (cnft-burn, cnft-vault, cutils)
oracles/*	1	pyth builds clean after the dep source-id fix; removed from .ghaignore

Several tokens/* projects that previously had Cargo.toml but no Quasar.toml (and were therefore listed in .github/.ghaignore) now build cleanly and have been added back to CI: spl-token-minter, external-delegate-token-master, nft-minter, nft-operations, token-swap. The oracles/pyth/quasar "build failed — outdated quasar-lang API" entry was removed for the same reason.

Test results

• tokens/escrow/quasar — 4/4 tests pass
• tokens/token-fundraiser/quasar — 5/5 tests pass
• basics/counter/quasar, basics/hello-solana/quasar — pass

All other migrated examples have quasar build green; their tests.rs files don't define new unit tests (most just have setup() helpers), so cargo test reports 0 passed; 0 failed — same as before the migration.

Cargo dependency hygiene fix

Earlier attempts hit a dual-source-id bug: when one quasar dep was { git = "..." } (no branch) and another was { git = "...", branch = "master" }, Cargo treated them as two distinct sources of the same crate even though they resolved to the same SHA. That broke trait-impl resolution (e.g. Token: Id not satisfied) because traits were imported from a different source-id.

This PR pins all quasar deps in every Cargo.toml to branch = "master" so they share one source-id.

Caveats / divergences from the Anchor siblings

• tokens/token-swap/quasar and tokens/external-delegate-token-master/quasar: the new #[derive(Seeds)] always emits the literal prefix first, so a couple of PDAs now derive with the prefix in a different position than the Anchor sibling. The programs are internally consistent (handlers, derive constraints, and tests all use the new order); only the on-chain addresses differ. This is documented in the file comments and the relevant commit messages.

• nft-minter, nft-operations, spl-token-minter keep manual MetadataCpi calls for runtime-supplied name/symbol/uri because the behaviour-style metadata(...) macro only accepts compile-time literals. The metadata: UncheckedAccount field type is preserved (the Metaplex program validates onchain).

References

• Quasar HEAD: 3d6fb0d8
• PR Add basics/favorites/poseidon solana-developers/program-examples#195: Refactor Accounts derive for external behavior plugins blueshift-gg/quasar#195
• PR Add basic/realloc/poseidon solana-developers/program-examples#196: Add metadata protocol account support blueshift-gg/quasar#196

---

Note

Medium Risk
Medium risk due to large-scale refactors across many Quasar examples (PDA derivation/seed ordering, account constraints, token metadata CPI wiring) and CI toolchain pinning; behavior should be equivalent but subtle address/constraint changes could break builds or tests.

Overview
Updates the entire set of quasar examples to compile against Quasar breaking changes from upstream PRs solana-developers#195/solana-developers#196, including new derive grammar (address = ... + #[derive(Seeds)]), init(idempotent) in place of init_if_needed, renamed program markers (SystemProgram, TokenProgram), new mint(...)/token(...) constraint syntax, CpiDynamic replacing DynCpiCall, and required bounded instruction strings (String<N>).

Adds seed-marker types where inline seeds = [...] was used and in several programs rebuilds PDA signer seed arrays manually, with some PDAs intentionally changing seed ordering to match the new derive behavior. Metaplex integrations are migrated to the extracted quasar-metadata crate and metadata creation stays as explicit CPI where runtime values are required.

CI is adjusted to pin the Quasar CLI install to a specific upstream revision to avoid a known quasar build regression, and .github/.ghaignore is reduced so more Quasar projects are built/tested again (with new Quasar.toml added for previously skipped projects).

^{Reviewed by Cursor Bugbot for commit 44f2dbd. Bugbot is set up for automated code reviews on this repo. Configure here.}