[P1] Add artifacted testnet acceptance workflow (spec-aligned FPC/FPCMultiAsset variants)

[ametel01]

Status (as of 2026-03-06)

This issue is still valid, but scope must stay aligned with current repo state.

What is already true in the codebase

• There is still no dedicated testnet acceptance CI workflow that archives evidence from verify + postdeploy smoke runs.
• Deploy manifest semantics are aligned to contracts.fpc (with optional fpc_artifact metadata).
• Post-deploy smoke is already artifact-driven (--fpc-artifact) and variant-aware.
• Current supported FPC artifact variants in scripts/manifest validation are FPC and FPCMultiAsset.

What is stale and removed from scope

• CreditFPC/credit variant wording is stale for current repository scripts and manifest schema and is removed from this issue scope.

Updated Scope

1. Add a workflow_dispatch testnet acceptance workflow under .github/workflows/.

• Inputs: manifest path/reference, network/RPC settings, and variant selection aligned to current artifacts (FPC, FPCMultiAsset, optional both mode).

2. In workflow execution, run:

• scripts/contract/verify-fpc-devnet-deployment.ts
• scripts/contract/devnet-postdeploy-smoke.ts --fpc-artifact <explicit artifact>

3. Archive evidence artifacts for each run:

• command logs/stdout-stderr
• selected artifact path + resolved contract variant
• manifest/network summary and pass/fail result

4. Update operator/deployment docs to include how to trigger this workflow and retrieve evidence artifacts.

• devnet-deployment-how-to.md

Files to change

• .github/workflows/ (new workflow)
• devnet-deployment-how-to.md

Optional only if workflow integration reveals a gap:

• scripts/contract/verify-fpc-devnet-deployment.ts
• scripts/contract/devnet-postdeploy-smoke.ts

Validation

• Trigger workflow with a valid manifest + credentials for:
  • FPC variant
  • FPCMultiAsset variant
• Confirm uploaded artifacts contain logs, selected artifact/variant metadata, and result summary.
• Confirm workflow relies on contracts.fpc + explicit artifact selection and does not require legacy fields.

Acceptance Criteria

• Maintainers can manually trigger testnet acceptance and retrieve archived evidence artifacts.
• Workflow supports current spec/tooling-aligned variant testing per invocation (or optional matrix/both mode).
• Workflow is aligned with current manifest + smoke semantics.

Dependency Notes

• Remove hard dependency on #133 (superseded/closed).
• #136 may remain related but is not a strict prerequisite for this workflow.