chore: refresh ai-skill

[Kiran01bm]

What and Why ?

The add-version-guard-resource skill was added in #33 and only had two
incidental touches since (#57, #63), but ~10 intervening PRs changed the
formats / schemas / workflows it teaches. Walked the skill end-to-end
against current resources.yaml + loader.go and fixed every
staleness an agent would hit today.

Markdown-only. No code changes.

Fixes

Spot	Was	Now
SKILL.md Step 1 (no-product STOP)	Stop on any missing product	Fall back to upstream product when AWS-flavored is missing (Valkey / Memcached pattern from #53); only stop if no product exists at all
SKILL.md Step 3 (native_type_pattern examples)	rds/AmazonAurora*/cluster, eks/Cluster, elastiCache/*/cluster	Actual current patterns from resources.yaml + note that * only matches whole path segments (partial-segment globs silently match nothing)
SKILL.md Step 4 (schema overview)	Standard = 3 fields; declarative = "EKS only"	Three real cycle shapes the standard adapter handles; declarative covers EKS and Lambda; inline lifecycle block; full field/action set incl. supported; accurate loader behavior (loader auto-fills schema: declarative when lifecycle: is present)
SKILL.md Step 6 (OpenSearch example)	native_type_pattern: "opensearch/Domain"	"elasticSearchService|OpenSearch Domain" (old value matched zero rows)
SKILL.md Step 6 (examples menu)	elasticache.yaml = "wildcard patterns"	Per-engine split (#53); the example file itself warns against wildcard + single product
SKILL.md Completion	Steered toward Go adapter	Steers toward declarative YAML; Go adapter is now exceptional (#63)
references/troubleshooting.md ("Non-Standard Schema")	schema: {resource}-adapter + "refer to EKS adapter"	schema: declarative + lifecycle: block, link to ADAPTERS.md; EKS Go adapter no longer exists
SKILL.md Step 7 footer	"Proceed to Step 7"	"Proceed to Step 8"

Driving PRs since #33

#36, #38, #42, #44, #45, #53, #54, #56, #62, #63.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7fc85d2c69

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove incorrect claim that Lambda uses declarative schema

This section says Lambda is a currently shipped schema: declarative resource, but the live default config defines lambda with schema: standard and no eol.lifecycle (pkg/config/defaults/resources.yaml lines 314-320). That mismatch will mislead anyone following the skill to model Lambda-like products as declarative when the repository’s actual pattern is standard, causing incorrect guidance and inconsistent configs.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Use unescaped OpenSearch alternation pattern in example table

The table shows native_type_pattern as elasticSearchService\|OpenSearch Domain, but the matcher in pkg/inventory/wiz/generic.go splits on literal | and does exact string comparison on each side. If users copy this escaped form, the first alternative becomes elasticSearchService\ and will never match, silently dropping Elasticsearch-native rows.

Useful? React with 👍 / 👎.

[Kiran01bm]

the test failures will be fixed in a subsequent pr - its a fall out from #66