fix(vscode): guide first calls and correct credential onboarding

[acedatacloud-dev]

After installing an individual VS Code MCP card, users can miss model selection and remain at the Copilot setup screen. The account MCP also asks for an application API key at Applications although it requires a platform management token. Guide model selection and first tool results, fix credential routing / labels, and tag the credential-page URL for the installed extension.

Changes:

• Update the fourteen target independent-card READMEs and their generator: model setup / Manage Language Models, Configure Tools, same-task polling, media and Usage checks, and separate model charges.
• Fix the MiniMax Applications link with a trailing period.
• Generate prompts for eighteen active codegen-managed extensions using vscode / referral / evergreen and a per-service extension content label from the current attribution contract. The account extension points to /console/platform-tokens and labels its credential Platform Token; command IDs stay stable.
• Add twenty-three runtime credential tests and run them in inventory CI. Hosted MCP URLs remain untagged; credential selection, SecretStorage, Bearer headers, tools, generation and billing are unchanged.

Validation:

• node --test scripts/test_vscode_credentials.js: 23 passed (routes, source labels, trimming, credential precedence, cancellation and clear command).
• python3 -m unittest: 34 passed.
• python3 scripts/marketing_readmes.py --check: 0 stale.
• python3 scripts/build_vscode_extensions.py --check and python3 scripts/check_readme_inventory.py: passed.
• Ruff check / format for the generator and git diff --check: passed; manual diff review completed.
• Current published baseline: model 0.1.2, bundle 2026.1012.24601 and fourteen 2026.1012.1 cards installed with official CLI in a fresh profile and activated in real VS Code 1.141 (16/16). Fourteen authenticated hosted MCP initialize/tools-list calls returned 200. Twelve original media tasks were queried successfully by their existing IDs only. No new generation or paid Chat was submitted.

Publication boundary: those runtime-host results describe the existing Marketplace baseline, not this PR's revised prompts. After an authorized merge, sync / downstream publish and another Marketplace package inspection are required before marking this update shipped. Eleven independent-card Chat checks remain pending a current paid-model allowance. Historical Usage re-read returned 401 with the existing management credential, so the prior billing evidence is not represented as a new successful audit.

Legacy relationship: this carries the credential-page portion of #831 onto current main using the current attribution convention. That old PR is still open and conflicting; its governance-dependent work is not silently marked complete. Retired Sora was untouched.