release(v1): ship curated private-prompt beta before Mainnet

[Joaco2603]

Release objective

Ship a narrow, honest, end-to-end product in two controlled stages:

1. Private Testnet beta: curated private PROMPT inventory and a complete buyer value loop.
2. Market V1: real-value settlement only after economy, creator payout, security, legal, and Mainnet gates are satisfied.

Testnet is useful product evidence, but it is not a real marketplace launch.

Scope guard

Market V1 supports one product type: PROMPT. Inventory is curated through operator-assisted creator onboarding. Agents, datasets, workflows, public self-service publishing, simulated credit packages, and general-purpose model execution are explicitly deferred.

Private Testnet beta gates

Quality and inventory

• Backend main is green and protected: fix(ci): restore a green and enforceable main pipeline #14
• Curated encrypted private-prompt publication works: feat(prompts): add a curated private-prompt publication pipeline #15
• Simulated wallet/payment behavior is removed from market mode: fix(wallet): authenticate wallet data and remove simulated production balances #16
• Authenticated purchase-to-access is complete: feat(marketplace): add authenticated Testnet purchase-to-access MVP flow #9

Customer journey

• Freighter authentication and protected sessions work: feat(auth): complete Freighter sign-in and protected sessions UI#5
• Browse -> purchase -> confirmation -> encrypted delivery works without fake data: feat(marketplace): ship the real prompt purchase and delivery journey UI#6
• UI CI protects the critical journey: test(ci): protect critical market journeys with automated checks UI#7

Release evidence

• Production-like Testnet staging and automated smoke evidence exist: chore(release): provision Testnet staging and an end-to-end market smoke test #17
• Landing claims/CTAs/trust surface match the shipped beta: feat(launch): turn the landing page into the trusted entry point for Market V1 Landing-page#1
• Five to ten curated prompts have named owners, support contacts, prices, and delivery validation.
• Operators can reconcile pending/failed purchases without direct database edits.

Market V1 additional gates

• Settlement asset and creator payout ADR is approved: docs(economy): decide the Market V1 settlement and creator payout model Smart-contracts#24
• Approved creator settlement is implemented and reconciled: feat(economy): implement the approved creator settlement model Smart-contracts#25
• Dependency provenance policy is complete: Security: define dependency provenance and reproducible audit policy Smart-contracts#9
• Independent security evidence and controlled Mainnet rollout are complete: security(release): complete audit evidence and controlled Mainnet rollout Smart-contracts#26
• Legal/trust content has qualified human review for launch jurisdictions.
• Support, incident response, refunds/disputes, and creator payout ownership have named humans.
• A capped Mainnet canary purchase settles, delivers, reconciles, and pays correctly before broader access.

Success metrics

• A new buyer can complete the supported journey without maintainer intervention.
• Purchase and delivery state is recoverable across reloads, RPC delays, and service restarts.
• No fictional balance, asset, execution, revenue, or transaction is presented as live data.
• Every settled Market V1 purchase has deterministic buyer, creator, platform, and delivery accounting.

Non-goals

• Multi-asset marketplace breadth.
• Open creator onboarding.
• Mainnet launch before independent security review.
• Privacy claims beyond the documented threat model and residual metadata leaks.

[Hollujay]

I would like to take on this issue, I will get it done efficiently as soon as possible.

[Joyful12-tech]

Hello Maintainer! I'd like to work on this issue. I can deliver it following the requirements and submit a quality PR within 2 days. Thank you!

[Joyful12-tech]

Hello Maintainer! I'd like to work on this issue. I can deliver it following the requirements and submit a quality PR within 2 days. Thank you!

[guptakumarranjeet150]

Hello! I'd like to work on this issue.

I can tackle release(v1): ship curated private-prompt beta before Mainnet. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in Stellar-AgentVerse/Backend
• Implementation: Structure backend handlers for release(v1): ship curated private-prompt beta before Mainnet with strict input validation, proper HTTP error codes, and idempotent execution.
• Testing: Cover implementation with end-to-end integration tests for standard and edge-case inputs.
• PR: Atomic commit with clean git hygiene and passing CI

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!