[herosjourney]

Problem

The plugin tells users to call Stability AI's Stable Image Core and Stable Image Ultra on Bedrock as stability.stable-image-core-v1:0 and stability.stable-image-ultra-v1:0. The current AWS model cards list v1:1 for both. v1:0 no longer appears on either card, on the Bedrock model-lifecycle pages, or in the Legacy/EOL tables. A user who copies the plugin's ID into code or a Terraform variable risks an invalid-model error at invoke time, and the generated migration report names an ID AWS no longer publishes.

The wrong ID sits in the shared pricing cache and lifecycle registry, so every skill that vendors those files (gcp-to-aws, azure-to-aws, agent-advisor) repeats it.

Fix

Correct the two IDs to v1:1 everywhere the plugin emits them, and cite the source next to the pricing rows.

• skills/shared/ai/bedrock-pricing-cache.md: both IDs in the Stability image table, plus a one-line note citing the two model cards and the verification date.
• skills/shared/ai/ai-model-lifecycle.md: both IDs in the Active Replacement column.
• skills/gcp-to-aws/references/phases/discover/discover-preview.md: the example target ID.
• scripts/model-id-lint.py: a comment that quoted the old ID.
• fixtures/migration-report-reference.html: the reference report's Stability row.
• Vendored twins under skills/{agent-advisor,azure-to-aws,gcp-to-aws}/references/vendored/ai/: regenerated with tools/sync-vendored.py, not hand-edited.

Source of truth: the Programmatic Access tables on the Stable Image Core 1.0 and Stable Image Ultra 1.0 model cards, read 2026-10-27. Both: bedrock-runtime model ID …-v1:1, in-Region us-west-2 only, no Geo or Global inference profile, lifecycle Active, EOL N/A.

What this PR does NOT do

• It does not change prices, tiers, lifecycle status, or any recommendation. Only the ID strings and one citation line change.
• It does not touch Stable Diffusion 3.5 Large. stability.sd3-5-large-v1:0 matches its model card and stays.
• It does not add the Stability models to the Capability Constraints table introduced in docs(aws-startup-advisor): refresh Bedrock model lifecycle for Oct 26 2026 #500. That table covers text models; image-model capability rows are a separate decision.
• It does not state whether v1:0 still resolves at runtime. The docs no longer mention it; nothing here was invoked against Bedrock.

Scope

Skills: shared/ai canonical files and their vendored twins in gcp-to-aws, azure-to-aws, agent-advisor; one gcp-to-aws phase doc. No new skill, no script behavior change.

Files: 10 paths (0 added, 10 modified, 0 deleted), +25 / −17.

Base: main at d7857c85 (includes #500). One commit, 5b829874.

Not touched: mapping guides, Clarify docs, bma-runtime.py, model-id-lint.py logic (comment only), any skill script.

Heads-up for in-flight PRs: #483 and feat/ai-mapping-guide-tiers edit bedrock-pricing-cache.md / ai-model-lifecycle.md and their twins. They should merge main after this lands and re-run tools/sync-vendored.py so the twins stay byte-identical.

Validation

Local gates, run from this branch against main at d7857c85, all exit 0:

• python3 plugins/aws-startup-advisor/tools/model-staleness.py --strict: pass.
• python3 plugins/aws-startup-advisor/scripts/model-id-lint.py: pass.
• python3 plugins/aws-startup-advisor/tools/sync-vendored.py --check: 59 vendored files byte-identical.
• mise -C plugins/aws-startup-advisor run ci: markdownlint 0 errors; lint:artifacts 85 artifacts / 0 errors; lint:skill-refs 1,404 refs / 0 missing; model-id, model-staleness, pricing, and consent-disclosure lints pass; plugin tests 513 passed; telemetry tests 279 passed; Heroku source-review tests 44 passed.
• python3 tools/validate.py: all validations passed.
• mise run validate: pass.
• gitleaks on upstream/main..HEAD: no leaks.

These are documentation and fixture changes. Nothing here was executed against a live Bedrock endpoint.

Limitations

• Whether stability.stable-image-core-v1:0 / -ultra-v1:0 still resolve on Bedrock is not stated in AWS docs and was not tested. Users with the old ID in production should check their own invocations.
• Both models are in-Region us-west-2 only. The pricing cache's Stability table is scoped to US East (N. Virginia) pricing; the price is the same, but the region note on that table is a separate follow-up.

Type of Change

• Documentation update
• New plugin
• New skill
• Bug fix
• CI/CD change
• Other

Checklist

• I have read the CONTRIBUTING guide
• My changes pass python3 tools/validate.py
• I have updated relevant documentation

Startup Advisor review checklist

• I have reviewed the full diff and understand all changes I am submitting.
• I have tested my changes and confirmed they work as intended.
• I have run mise -C plugins/aws-startup-advisor run ci and all checks pass.
• I have disclosed any known issues, limitations, or untested scenarios.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[leon1418]

[🤖 AI review 🤖]

Reviewed all 10 changed files at 5b829874d4a8ca63d3848801e54659090058de25, including the vendored copies and unchanged model-ID consumers. No substantive findings. The current AWS model cards list both Core and Ultra as v1:1.

Local validation: 513 plugin tests and 562 agent-advisor tests passed, along with model-ID, lifecycle freshness, pricing coverage, artifact, vendored-parity, repository validation, and diff checks. No live Bedrock invocation was performed; this review does not establish whether the old IDs still resolve.

Approval recommended for the human reviewer. Merge readiness remains subject to the repository checks and required approvals.