fix: config.meta is not a dict attribute, use config.get('meta', {})

[tejas-sigma]

Bug

Every config.meta.get(x) call in v1.0.6 crashes at runtime:

'dbt.context.providers.RuntimeConfigObject object' has no attribute 'meta'

The live config context object inside a materialization/relation macro doesn't expose .meta as a plain attribute — only .get('key', default) works. node.config (a rendered dict from the manifest, used correctly in cortex_skill/create.sql:136) is a different object, which is presumably why that one line wasn't affected and this shipped without being caught locally.

Confirmed against dbt-sos's Slim CI: every model using the cortex_agent, cortex_skill, or cortex_mcp_server materializations fails to compile — 13/17 cortex_agent/cortex_skill models errored in a real build, 100% reproducible, same stack trace every time.

Fix

All 24 call sites across cortex_agent.sql, cortex_agent/create.sql, cortex_skill/create.sql, and cortex_mcp_server/create.sql changed from config.meta.get(x) to config.get('meta', {}).get(x) — the same pattern dbt-cortex-search-service already uses correctly (config.get('meta', default={})).

No behavior change beyond the fix itself — same fallback-to-legacy-top-level-key logic on every call site, just using a config accessor that actually exists.