Docs: per-port verify tables give a Python command that does not run and the wrong C# binary #492

Where

• docs/features/migrations-and-drift.md lines 373-381, the "Drift verify commands per port" table.
• docs/features/templates-and-payloads.md lines 657-663, the "Drift detection: verify" table.
• Shorter copies of the same claims: docs/features/requirements.md lines 350 and 431, agent-context/skills/metaobjects-verify/references/requirements.md line 29, README.md line 169 and docs/ports/python.md line 889.

What they say today, and what is true

• Python: both tables give python -m metaobjects.render.verify. That module has no main and no __main__, so the command does not run. The command is metaobjects verify (server/python/pyproject.toml line 43; docs/features/cli.md lines 210-211).
• C#: migrations-and-drift.md line 380 gives meta verify ./metadata --templates ./prompts. meta is the Node CLI; the C# command is dotnet meta verify.
• Bare verify: neither table says what a run with no flags does. Since fix(cli): run codegen and template gates on bare verify in every port #475 and feat(csharp): run the codegen gate on bare verify via csharp.outDir #477, a bare run in every port checks generated code, prompt templates and the requirement ledger, and skips a check that has no config with a one-line note (docs/features/cli.md lines 65-80).

Expected change

• Rewrite both tables with one row per port: the bare command (meta verify, dotnet meta verify, mvn metaobjects:verify, metaobjects verify), what a bare run checks, the config each check needs (from docs/features/cli.md lines 67-75), and how to run one check alone.
• Keep meta verify --db as its own line: it is opt-in and Node-only.
• Replace python -m metaobjects.render.verify everywhere it appears.
• If you edit the agent-context/ file, regenerate the matching fixture under fixtures/agent-context-conformance/ (for example fixtures/agent-context-conformance/ts-requirements/expected/.claude/skills/metaobjects-verify/references/requirements.md).

Test or check to add
No test covers these tables today. Optional: a small check that fails if python -m metaobjects.render.verify appears anywhere under docs/. Otherwise the reviewer checks the new tables against docs/features/cli.md lines 65-80. Run scripts/ci-local.sh --quick before opening the PR.

Size: under an hour.

New here? CONTRIBUTING.md covers setup and the local checks. Comment on this issue before you start so two people do not pick it up.