feat: ACP SDK v2 → v3 migration Qchainer prep agent trader showcase

[drQedwards]

Showcase Project

What shipped

• Project slug: acp-sdk-v2-to-v3-migration
• Project title: ACP SDK v2 → v3 Migration
• Builder name and URL: Dr. Q (@jk_drq) / Qchain — https://x.com/jk_drq
• EconomyOS primitives used: wallet, acp
• Public proof:
  • Offline self-check + redacted dry-run report (no keys, no mainnet txs)
  • X video/watch surface: @jk_drq Distorted Face Piano Space — https://x.com/i/spaces/1dKrPPWnNDzJX
• Optional soul.md: showcase/acp-sdk-v2-to-v3-migration/soul.md (public/redacted)

Project package

• Added or updated showcase/acp-sdk-v2-to-v3-migration/showcase.json
• Added demo artifacts, prompt, proof, and redacted report
• Added reusable skill under showcase/acp-sdk-v2-to-v3-migration/skills/acp-sdk-v2-to-v3-migration/
• Used top-level skills/<skill-name>/ only when the skill is shared across projects (this skill is project-specific)
• Set skills[].sourcePath in showcase.json
• Linked all public artifacts from the manifest
• Included exactly three feedback prompts
• hidden: true not set — publish card after merge
• Linked soul.md as public/redacted agent context

Skill standard

• Skill path: showcase/acp-sdk-v2-to-v3-migration/skills/acp-sdk-v2-to-v3-migration
• SKILL.md includes when to use it and when not to use it
• Inputs, tools, credentials, and preconditions are explicit
• Approval gates are listed for spending / live mode / dashboard upgrade
• Stop conditions and handoff rules are listed
• Validation checks and output contract are included

Safety and redaction

• No card numbers, CVVs, OTPs, magic links, API keys, access tokens, private prompts, wallet material, or private account records are published
• Live workflow evidence is redacted (offline dry-run only)
• Public/private boundaries are explained
• Optional soul.md does not include private instructions, credentials, account data, wallet material, or operational secrets
• X Space is public watch-page only — no scraped/re-hosted audio binary

Video / X proof

• Builder X: https://x.com/jk_drq
• Primary piano Space: https://x.com/i/spaces/1dKrPPWnNDzJX (Distorted Face Piano)
• Manifest wiring:
  • links.video / links.share → Space URL
  • visual.videoLabel → names X
  • visual.videoUrl omitted (Spaces have no stable public video.twimg.com mp4)
  • visual.posterUrl → package poster PNG
• Notes: showcase/acp-sdk-v2-to-v3-migration/proof/jk-drq-piano-spaces.md

Validation ran

node showcase/acp-sdk-v2-to-v3-migration/scripts/self-check.mjs   # 10/10 pass
node showcase/acp-sdk-v2-to-v3-migration/examples/v3-provider.mjs
node showcase/acp-sdk-v2-to-v3-migration/examples/v3-client.mjs
node scripts/validate-showcase.mjs                               # manifests OK

Publish path

After this PR is approved and merged to main, changes under showcase/** trigger the EconomyOS docs sync. The accepted manifest is published into /community#showcase by the docs workflow.

[drQedwards]

Public X video proof wired

Builder: @jk_drq

Primary piano Space used as links.video / links.share:

• Distorted Face Piano — https://x.com/i/spaces/1dKrPPWnNDzJX

Manifest notes:

• visual.videoLabel names X
• visual.videoUrl omitted (Spaces page, no stable public amplify mp4)
• local poster kept for the card
• proof write-up: showcase/acp-sdk-v2-to-v3-migration/proof/jk-drq-piano-spaces.md

If you have additional piano Space URLs/status clips on @jk_drq that should be listed alongside this one, drop them in-thread and I’ll append artifacts.

[drQedwards]

Telegram demo surface

Public desk bot wired into the showcase:

• https://t.me/Qchaingoldbot (@Qchaingoldbot)
• Manifest: links.demo + artifact
• Notes: showcase/acp-sdk-v2-to-v3-migration/proof/telegram-qchaingoldbot.md

X piano Space remains links.video / links.share.

[drQedwards]

Pipeline is green on the fork — needs workflow approval upstream

Pushed 1998f69, which adds a package-scoped CI workflow and declares the builder association.

What's in the commit

• .github/workflows/showcase-acp-sdk-v2-to-v3-migration.yml — gated on showcase/acp-sdk-v2-to-v3-migration/**
• showcase.json — builder.association: "champion", asserted in CI

Steps the workflow runs

1. node scripts/validate-showcase.mjs — manifest validation
2. node --check on v3-provider.mjs, v3-client.mjs, phase-event-map.mjs, v2-provider.legacy.mjs
3. npm run check — 10 offline self-check assertions
4. Skill installability into ~/.agents/skills and ~/.claude/skills
5. Proof artifact presence — piano Spaces notes, offline validation receipt, Telegram notes, poster, soul.md

Result on the fork — run 30723206354, job package self-check, success, all 10 steps passing:

github author_association : N/A
declared association      : champion
builder.association = champion
Validated 55 showcase project manifest(s).
10 checks passed

On association — GitHub's author_association is derived from repository permissions and cannot be set by a contributor. champion is a manifest-level declaration only. The workflow prints GitHub's derived value alongside the declared one in the job summary so the distinction is visible in review rather than implied.

The ask

Both typecheck and the new workflow have been sitting at action_required on this repo since 18:47 UTC — every run is 0s, nothing has executed upstream. Fork PRs from unaffiliated accounts need a maintainer to approve workflow runs.

Could someone approve the runs on this PR? That's the only thing between this and a reviewable green PR — the code side is done and passing. Happy to re-push if you'd prefer the workflow scoped differently or dropped entirely in favour of the existing typecheck job.

[github-actions]

This is a really impressive and detailed migration kit, thanks for putting it together! The side-by-side examples and the offline self-check are great touches.

There are a couple of structural things that are pretty far off the standard showcase pattern, which we should probably align on before merging:

1. Custom CI Workflow: This PR adds a new file to .github/workflows/. Showcase packages are meant to be validated by the repo's existing CI, not to add their own. This isn't a pattern we can scale to all showcase items, as it would make CI maintenance really complex. Could this workflow file be removed?

2. Embedded Application: The PR also includes a package.json and runnable scripts inside the showcase/ directory. The established pattern is to keep the showcase package as data/docs (manifest, markdown, images) and link to the runnable code in an external repository (like your fork). This keeps the main repo focused on the showcase data itself.

I've also left a small suggestion inline for the tagline. One other copy note: the topics list in the manifest should be trimmed to just the standard values from the contributor guide (e.g., skills, agents). The current list has several extra ones like sdk and typescript.

Let me know what you think!

Suggested edits (couldn't be anchored inline — copy manually)

showcase/acp-sdk-v2-to-v3-migration/showcase.json (around line 4)
Totally optional, but the contributor guide suggests a shorter, verb-led tagline. How about something like this?

  "tagline": "Migrate ACP Node SDK integrations from v2 callbacks to v3 events",

---

Refreshed after a new push. Any inline suggestions from the first pass may now be stale.