@raishin/vanguard-frontier-agentic 3.19.0 → 3.20.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +2 -2
- package/.claude-plugin/plugin.json +8 -1
- package/.cursor-plugin/plugin.json +8 -1
- package/.github/plugin/marketplace.json +1 -1
- package/README.md +21 -21
- package/agents/AGENTS.md +4 -4
- package/agents/README.md +7 -7
- package/agents/alibaba/alibaba-tablestore-architect-agent/AGENT.md +54 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/codex.toml +11 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/metadata.json +39 -0
- package/agents/aws/aws-dynamodb-patterns-agent/AGENT.md +53 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/codex.toml +23 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/copilot.agent.md +42 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/cursor.agent.md +38 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/gemini.agent.md +38 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/aws/aws-dynamodb-patterns-agent/metadata.json +39 -0
- package/agents/azure/azure-cosmosdb-application-developer-agent/metadata.json +4 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/AGENT.md +53 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/codex.toml +23 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/copilot.agent.md +42 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/cursor.agent.md +37 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/gemini.agent.md +38 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/metadata.json +38 -0
- package/agents/gcp/gcp-bigtable-architect-agent/AGENT.md +54 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/codex.toml +11 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/gcp/gcp-bigtable-architect-agent/metadata.json +39 -0
- package/agents/huawei/huawei-geminidb-architect-agent/AGENT.md +54 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/codex.toml +11 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/huawei/huawei-geminidb-architect-agent/metadata.json +38 -0
- package/agents/oci/oci-nosql-database-architect-agent/AGENT.md +54 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/codex.toml +11 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/cursor.agent.md +39 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/oci/oci-nosql-database-architect-agent/metadata.json +39 -0
- package/agents/oci/oci-nosql-pattern-agent/AGENT.md +53 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/codex.toml +23 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/copilot.agent.md +42 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/cursor.agent.md +38 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/gemini.agent.md +38 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/oci/oci-nosql-pattern-agent/metadata.json +38 -0
- package/catalog/agents.json +204 -1
- package/catalog/asset-integrity.json +601 -61
- package/catalog/install-roles.json +19 -1
- package/catalog/model-assignments.json +231 -0
- package/catalog/skill-manifest.json +1603 -56
- package/catalog/skills.json +314 -14
- package/package.json +7 -2
- package/plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json +1 -1
- package/powers/vanguard-alibaba/POWER.md +1 -1
- package/powers/vanguard-aws/POWER.md +1 -1
- package/powers/vanguard-azure/POWER.md +1 -1
- package/powers/vanguard-gcp/POWER.md +1 -1
- package/powers/vanguard-huawei/POWER.md +1 -1
- package/powers/vanguard-oci/POWER.md +1 -1
- package/skills/alibaba/README.md +2 -1
- package/skills/alibaba/alibaba-maestro/SKILL.md +2 -1
- package/skills/alibaba/alibaba-tablestore-architect/SKILL.md +69 -0
- package/skills/alibaba/alibaba-tablestore-architect/metadata.json +28 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/live.md +110 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/offline.md +119 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit.md +22 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/evidence-ledger.md +87 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/operations.md +190 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/tablestore-design-guide.md +159 -0
- package/skills/aws/aws-documentdb-architect/SKILL.md +43 -0
- package/skills/aws/aws-documentdb-architect/metadata.json +26 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit/live.md +135 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit/offline.md +127 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit.md +23 -0
- package/skills/aws/aws-documentdb-architect/references/evidence-ledger.md +52 -0
- package/skills/aws/aws-documentdb-architect/references/official-sources.md +15 -0
- package/skills/aws/aws-documentdb-architect/references/operations.md +165 -0
- package/skills/aws/aws-documentdb-architect/references/safety-checklist.md +22 -0
- package/skills/aws/aws-documentdb-architect/references/workflow-and-output.md +22 -0
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/SKILL.md +5 -3
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/metadata.json +7 -3
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/consistency-indexing-replication.md +103 -0
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/evidence-ledger.md +38 -0
- package/skills/aws/aws-dynamodb-patterns/CHANGELOG.md +87 -0
- package/skills/aws/aws-dynamodb-patterns/README.md +132 -0
- package/skills/aws/aws-dynamodb-patterns/SKILL.md +82 -0
- package/skills/aws/aws-dynamodb-patterns/assets/bedrock-embedding-input.json +6 -0
- package/skills/aws/aws-dynamodb-patterns/assets/content-review.json +6 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table-with-lsi.json +41 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table.json +27 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table.sh +37 -0
- package/skills/aws/aws-dynamodb-patterns/assets/embedding-flow.py +89 -0
- package/skills/aws/aws-dynamodb-patterns/assets/query-input.json +13 -0
- package/skills/aws/aws-dynamodb-patterns/assets/query-pages.mjs +54 -0
- package/skills/aws/aws-dynamodb-patterns/assets/stream-read-policy.json +11 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table-index-read-policy.json +20 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table-resource-policy.json +22 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table.cfn.yaml +55 -0
- package/skills/aws/aws-dynamodb-patterns/assets/typed-vector-item.json +15 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-create-table.json +23 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-search-policy.json +11 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-search.json +10 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-table.cfn.yaml +41 -0
- package/skills/aws/aws-dynamodb-patterns/evals/audit.test.py +87 -0
- package/skills/aws/aws-dynamodb-patterns/evals/backup-restore.test.py +163 -0
- package/skills/aws/aws-dynamodb-patterns/evals/commands.test.py +185 -0
- package/skills/aws/aws-dynamodb-patterns/evals/create-table.test.py +99 -0
- package/skills/aws/aws-dynamodb-patterns/evals/data-vectors-maintenance.test.py +201 -0
- package/skills/aws/aws-dynamodb-patterns/evals/embedding-commands.test.py +162 -0
- package/skills/aws/aws-dynamodb-patterns/evals/embedding-flow.test.py +167 -0
- package/skills/aws/aws-dynamodb-patterns/evals/eval.md +328 -0
- package/skills/aws/aws-dynamodb-patterns/evals/evals.json +185 -0
- package/skills/aws/aws-dynamodb-patterns/evals/modes.test.py +195 -0
- package/skills/aws/aws-dynamodb-patterns/evals/operations.test.py +288 -0
- package/skills/aws/aws-dynamodb-patterns/evals/query-pages.test.mjs +156 -0
- package/skills/aws/aws-dynamodb-patterns/evals/readme-and-loading.test.py +69 -0
- package/skills/aws/aws-dynamodb-patterns/evals/verify.py +166 -0
- package/skills/aws/aws-dynamodb-patterns/metadata.json +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/README.md +32 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit/live.md +64 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit/offline.md +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit.md +65 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/aws-cli.md +206 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup/on-demand.md +36 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup/pitr.md +41 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup.md +27 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/design.md +47 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/embedding.md +200 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/feature-plan.md +56 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/help.md +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/performance-test.md +95 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/recovery-target.md +47 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/refactor.md +82 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore/on-demand.md +32 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore/pitr.md +42 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore.md +76 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/select.md +22 -0
- package/skills/aws/aws-dynamodb-patterns/references/data-types-and-vectors.md +175 -0
- package/skills/aws/aws-dynamodb-patterns/references/embedding-integrations.md +237 -0
- package/skills/aws/aws-dynamodb-patterns/references/encryption.md +156 -0
- package/skills/aws/aws-dynamodb-patterns/references/evidence-index.md +116 -0
- package/skills/aws/aws-dynamodb-patterns/references/evidence-ledger.md +373 -0
- package/skills/aws/aws-dynamodb-patterns/references/iam-and-access.md +173 -0
- package/skills/aws/aws-dynamodb-patterns/references/language-adapters.md +251 -0
- package/skills/aws/aws-dynamodb-patterns/references/lsi-vs-gsi.md +116 -0
- package/skills/aws/aws-dynamodb-patterns/references/maintenance.md +56 -0
- package/skills/aws/aws-dynamodb-patterns/references/modeling.md +131 -0
- package/skills/aws/aws-dynamodb-patterns/references/monitoring.md +137 -0
- package/skills/aws/aws-dynamodb-patterns/references/official-sources.md +34 -0
- package/skills/aws/aws-dynamodb-patterns/references/operations.md +130 -0
- package/skills/aws/aws-dynamodb-patterns/references/provisioning.md +110 -0
- package/skills/aws/aws-dynamodb-patterns/references/recovery-and-replicas.md +148 -0
- package/skills/aws/aws-dynamodb-patterns/references/runtime-contract.md +140 -0
- package/skills/aws/aws-dynamodb-patterns/references/safety-checklist.md +35 -0
- package/skills/aws/aws-dynamodb-patterns/references/sources.md +170 -0
- package/skills/aws/aws-dynamodb-patterns/references/streams-and-dax.md +160 -0
- package/skills/aws/aws-dynamodb-patterns/references/workflow-and-output.md +34 -0
- package/skills/aws/aws-dynamodb-patterns/references/workflow.md +133 -0
- package/skills/aws/aws-dynamodb-patterns/scripts/review_due.py +61 -0
- package/skills/aws/aws-dynamodb-patterns/scripts/select_mode.py +127 -0
- package/skills/aws/aws-keyspaces-architect/SKILL.md +43 -0
- package/skills/aws/aws-keyspaces-architect/metadata.json +26 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit/live.md +118 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit/offline.md +125 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit.md +22 -0
- package/skills/aws/aws-keyspaces-architect/references/evidence-ledger.md +49 -0
- package/skills/aws/aws-keyspaces-architect/references/official-sources.md +15 -0
- package/skills/aws/aws-keyspaces-architect/references/operations.md +154 -0
- package/skills/aws/aws-keyspaces-architect/references/safety-checklist.md +22 -0
- package/skills/aws/aws-keyspaces-architect/references/workflow-and-output.md +22 -0
- package/skills/aws/aws-maestro/SKILL.md +1 -1
- package/skills/aws/aws-maestro/metadata.json +1 -1
- package/skills/aws/aws-maestro/references/workflow-and-output.md +1 -0
- package/skills/azure/azure-cosmosdb-application-developer/SKILL.md +4 -2
- package/skills/azure/azure-cosmosdb-application-developer/metadata.json +1 -1
- package/skills/azure/azure-cosmosdb-pattern/CHANGELOG.md +10 -0
- package/skills/azure/azure-cosmosdb-pattern/README.md +102 -0
- package/skills/azure/azure-cosmosdb-pattern/SKILL.md +69 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/account.arm.json +59 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/content-review.json +9 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/indexing-policy.json +7 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/order.json +10 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/provision.sh +32 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/runtime.mjs +99 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/vector-indexing-policy.json +7 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/vector-policy.json +3 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/eval.md +32 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/fixtures/recovery-continuous.json +28 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/prompts.json +24 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/report.md +54 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/runtime.test.mjs +146 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/source-evidence.json +28 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/test_package.py +355 -0
- package/skills/azure/azure-cosmosdb-pattern/metadata.json +25 -0
- package/skills/azure/azure-cosmosdb-pattern/references/access-control.md +42 -0
- package/skills/azure/azure-cosmosdb-pattern/references/change-feed-and-integrations.md +31 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/live.md +17 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/offline.md +15 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit.md +8 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/azure-cli.md +39 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/continuous.md +30 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/periodic.md +28 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup.md +11 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/design.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/feature-plan.md +18 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/help.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/performance-test.md +24 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/recovery-target.md +30 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/refactor.md +14 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-deleted-resource.md +55 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-new-account.md +50 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/periodic-support.md +27 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/select.md +11 -0
- package/skills/azure/azure-cosmosdb-pattern/references/data-types-and-vectors.md +51 -0
- package/skills/azure/azure-cosmosdb-pattern/references/embedding-integrations.md +56 -0
- package/skills/azure/azure-cosmosdb-pattern/references/encryption.md +53 -0
- package/skills/azure/azure-cosmosdb-pattern/references/evidence-index.md +72 -0
- package/skills/azure/azure-cosmosdb-pattern/references/evidence-ledger.md +174 -0
- package/skills/azure/azure-cosmosdb-pattern/references/indexing-and-capacity.md +37 -0
- package/skills/azure/azure-cosmosdb-pattern/references/language-adapters.md +112 -0
- package/skills/azure/azure-cosmosdb-pattern/references/maintenance.md +19 -0
- package/skills/azure/azure-cosmosdb-pattern/references/modeling.md +44 -0
- package/skills/azure/azure-cosmosdb-pattern/references/monitoring.md +23 -0
- package/skills/azure/azure-cosmosdb-pattern/references/provisioning.md +61 -0
- package/skills/azure/azure-cosmosdb-pattern/references/recovery.md +31 -0
- package/skills/azure/azure-cosmosdb-pattern/references/replication.md +22 -0
- package/skills/azure/azure-cosmosdb-pattern/references/runtime-contract.md +43 -0
- package/skills/azure/azure-cosmosdb-pattern/references/sources.md +61 -0
- package/skills/azure/azure-cosmosdb-pattern/references/workflow.md +18 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/recovery_guard.py +96 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/review_due.py +26 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/select_mode.py +108 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/validate_assets.py +53 -0
- package/skills/azure/azure-cosmosdb-platform-operator/SKILL.md +6 -2
- package/skills/azure/azure-cosmosdb-platform-operator/metadata.json +6 -3
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/live.md +180 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/offline.md +160 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit.md +26 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/consistency-capacity-security.md +136 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/cosmosdb-platform-operations.md +1 -1
- package/skills/azure/azure-cosmosdb-platform-operator/references/evidence-ledger.md +242 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations-cassandra.md +178 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations-mongodb.md +202 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations.md +126 -0
- package/skills/azure/azure-maestro/SKILL.md +1 -0
- package/skills/gcp/README.md +2 -1
- package/skills/gcp/gcp-bigtable-architect/SKILL.md +71 -0
- package/skills/gcp/gcp-bigtable-architect/metadata.json +28 -0
- package/skills/gcp/gcp-bigtable-architect/references/bigtable-design-guide.md +156 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit/live.md +122 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit/offline.md +140 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit.md +21 -0
- package/skills/gcp/gcp-bigtable-architect/references/evidence-ledger.md +83 -0
- package/skills/gcp/gcp-bigtable-architect/references/operations.md +111 -0
- package/skills/gcp/gcp-firebase-developer/SKILL.md +6 -3
- package/skills/gcp/gcp-firebase-developer/metadata.json +14 -4
- package/skills/gcp/gcp-firebase-developer/references/commands/audit/live.md +124 -0
- package/skills/gcp/gcp-firebase-developer/references/commands/audit/offline.md +146 -0
- package/skills/gcp/gcp-firebase-developer/references/commands/audit.md +27 -0
- package/skills/gcp/gcp-firebase-developer/references/evidence-ledger.md +190 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore-mongodb-operations.md +189 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore-operations.md +202 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore.md +122 -0
- package/skills/gcp/gcp-maestro/SKILL.md +2 -1
- package/skills/huawei/README.md +2 -1
- package/skills/huawei/huawei-gaussdb-rds-dba/SKILL.md +7 -4
- package/skills/huawei/huawei-gaussdb-rds-dba/metadata.json +12 -4
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/live.md +68 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/offline.md +106 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit.md +23 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/dds-operations.md +135 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/evidence-ledger.md +87 -0
- package/skills/huawei/huawei-geminidb-architect/SKILL.md +68 -0
- package/skills/huawei/huawei-geminidb-architect/metadata.json +26 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit/live.md +68 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit/offline.md +108 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit.md +23 -0
- package/skills/huawei/huawei-geminidb-architect/references/evidence-ledger.md +83 -0
- package/skills/huawei/huawei-geminidb-architect/references/geminidb-design-guide.md +114 -0
- package/skills/huawei/huawei-geminidb-architect/references/operations.md +135 -0
- package/skills/huawei/huawei-maestro/SKILL.md +2 -1
- package/skills/ionos/ionos-live-database-lifecycle-guard/SKILL.md +2 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/live.md +87 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/offline.md +109 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit.md +27 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/evidence-ledger.md +69 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/mongodb-operations.md +220 -0
- package/skills/oci/README.md +6 -1
- package/skills/oci/oci-nosql-database-architect/SKILL.md +73 -0
- package/skills/oci/oci-nosql-database-architect/metadata.json +28 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit/live.md +136 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit/offline.md +150 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit.md +28 -0
- package/skills/oci/oci-nosql-database-architect/references/evidence-ledger.md +96 -0
- package/skills/oci/oci-nosql-database-architect/references/nosql-design-guide.md +194 -0
- package/skills/oci/oci-nosql-database-architect/references/operations.md +194 -0
- package/skills/oci/oci-nosql-database-architect/references/sdk-matrix.md +43 -0
- package/skills/oci/oci-nosql-pattern/CHANGELOG.md +8 -0
- package/skills/oci/oci-nosql-pattern/README.md +81 -0
- package/skills/oci/oci-nosql-pattern/SKILL.md +62 -0
- package/skills/oci/oci-nosql-pattern/assets/content-review.json +10 -0
- package/skills/oci/oci-nosql-pattern/assets/create-table.sh +32 -0
- package/skills/oci/oci-nosql-pattern/assets/index-keys.json +11 -0
- package/skills/oci/oci-nosql-pattern/assets/migrator-export.json +22 -0
- package/skills/oci/oci-nosql-pattern/assets/migrator-import.json +29 -0
- package/skills/oci/oci-nosql-pattern/assets/orders.ddl +9 -0
- package/skills/oci/oci-nosql-pattern/assets/orders.tf +46 -0
- package/skills/oci/oci-nosql-pattern/assets/query-pages.mjs +33 -0
- package/skills/oci/oci-nosql-pattern/assets/query.json +13 -0
- package/skills/oci/oci-nosql-pattern/assets/query.sql +1 -0
- package/skills/oci/oci-nosql-pattern/assets/recovery-manifest.example.json +35 -0
- package/skills/oci/oci-nosql-pattern/assets/row.json +10 -0
- package/skills/oci/oci-nosql-pattern/assets/table-limits.json +6 -0
- package/skills/oci/oci-nosql-pattern/evals/cli-shapes.json +222 -0
- package/skills/oci/oci-nosql-pattern/evals/eval.md +26 -0
- package/skills/oci/oci-nosql-pattern/evals/prompts.json +89 -0
- package/skills/oci/oci-nosql-pattern/evals/report.md +41 -0
- package/skills/oci/oci-nosql-pattern/evals/test_package.py +350 -0
- package/skills/oci/oci-nosql-pattern/evals/test_runtime.mjs +77 -0
- package/skills/oci/oci-nosql-pattern/metadata.json +25 -0
- package/skills/oci/oci-nosql-pattern/references/access.md +29 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit/live.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit/offline.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit.md +6 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup/migrator.md +12 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup/sdk.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup.md +7 -0
- package/skills/oci/oci-nosql-pattern/references/commands/design.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/feature-plan.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/help.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/performance-test.md +12 -0
- package/skills/oci/oci-nosql-pattern/references/commands/refactor.md +9 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore/migrator.md +13 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore/sdk.md +11 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/select.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/embedding-integrations.md +25 -0
- package/skills/oci/oci-nosql-pattern/references/encryption.md +18 -0
- package/skills/oci/oci-nosql-pattern/references/evidence-index.md +44 -0
- package/skills/oci/oci-nosql-pattern/references/evidence-ledger.md +73 -0
- package/skills/oci/oci-nosql-pattern/references/indexes.md +19 -0
- package/skills/oci/oci-nosql-pattern/references/language-adapters.md +160 -0
- package/skills/oci/oci-nosql-pattern/references/maintenance.md +15 -0
- package/skills/oci/oci-nosql-pattern/references/modeling.md +26 -0
- package/skills/oci/oci-nosql-pattern/references/monitoring.md +21 -0
- package/skills/oci/oci-nosql-pattern/references/provisioning.md +44 -0
- package/skills/oci/oci-nosql-pattern/references/recovery-boundary.md +32 -0
- package/skills/oci/oci-nosql-pattern/references/replicas.md +18 -0
- package/skills/oci/oci-nosql-pattern/references/runtime-contract.md +23 -0
- package/skills/oci/oci-nosql-pattern/references/sources.md +57 -0
- package/skills/oci/oci-nosql-pattern/references/ttl.md +19 -0
- package/skills/oci/oci-nosql-pattern/references/types-and-vectors.md +27 -0
- package/skills/oci/oci-nosql-pattern/scripts/check_recovery.py +52 -0
- package/skills/oci/oci-nosql-pattern/scripts/review_due.py +32 -0
- package/skills/oci/oci-nosql-pattern/scripts/select_mode.py +96 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/SKILL.md +43 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/metadata.json +25 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/live.md +90 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/offline.md +112 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit.md +24 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/evidence-ledger.md +93 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/official-sources.md +15 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/operations.md +216 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/safety-checklist.md +22 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/workflow-and-output.md +22 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/SKILL.md +43 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/metadata.json +24 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/live.md +99 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/offline.md +114 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit.md +24 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/evidence-ledger.md +43 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/official-sources.md +14 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/operations.md +114 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/safety-checklist.md +22 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/workflow-and-output.md +22 -0
- package/templates/nosql-audit-template.md +127 -0
- package/templates/nosql-operations-template.md +60 -0
- package/tests/_generate_maestro_routing_fixtures.py +11 -0
- package/tests/fixtures/README.md +2 -2
- package/tests/fixtures/alibaba-maestro-routing/expected/050-happy-tablestore-partition-key.json +6 -0
- package/tests/fixtures/alibaba-maestro-routing/expected/adv-tablestore-not-polardb.json +6 -0
- package/tests/fixtures/alibaba-maestro-routing/inputs/050-happy-tablestore-partition-key.json +7 -0
- package/tests/fixtures/alibaba-maestro-routing/inputs/adv-tablestore-not-polardb.json +7 -0
- package/tests/fixtures/alibaba-maestro-routing/taxonomy.json +13 -0
- package/tests/fixtures/aws-maestro-routing/expected/042-happy-dynamodb-patterns.json +6 -0
- package/tests/fixtures/aws-maestro-routing/expected/043-happy-dynamodb-vector-index.json +6 -0
- package/tests/fixtures/aws-maestro-routing/inputs/042-happy-dynamodb-patterns.json +7 -0
- package/tests/fixtures/aws-maestro-routing/inputs/043-happy-dynamodb-vector-index.json +7 -0
- package/tests/fixtures/aws-maestro-routing/taxonomy.json +15 -1
- package/tests/fixtures/azure-maestro-routing/expected/028-happy-cosmosdb-pattern-feature-plan.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/029-happy-cosmosdb-pattern-refactor.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-hot-partition-not-key-vault.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-partition-key-not-key-vault.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-throttling-investigation.json +6 -0
- package/tests/fixtures/azure-maestro-routing/inputs/028-happy-cosmosdb-pattern-feature-plan.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/029-happy-cosmosdb-pattern-refactor.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-hot-partition-not-key-vault.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-partition-key-not-key-vault.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-throttling-investigation.json +7 -0
- package/tests/fixtures/azure-maestro-routing/taxonomy.json +21 -2
- package/tests/fixtures/gcp-maestro-routing/expected/049-happy-bigtable-row-key.json +6 -0
- package/tests/fixtures/gcp-maestro-routing/expected/adv-bigtable-not-firestore.json +8 -0
- package/tests/fixtures/gcp-maestro-routing/inputs/049-happy-bigtable-row-key.json +7 -0
- package/tests/fixtures/gcp-maestro-routing/inputs/adv-bigtable-not-firestore.json +7 -0
- package/tests/fixtures/gcp-maestro-routing/taxonomy.json +15 -0
- package/tests/fixtures/huawei-maestro-routing/expected/050-happy-geminidb-cassandra-partition.json +6 -0
- package/tests/fixtures/huawei-maestro-routing/expected/adv-geminidb-mongo-routes-dds.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/inputs/050-happy-geminidb-cassandra-partition.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/inputs/adv-geminidb-mongo-routes-dds.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/taxonomy.json +15 -0
- package/tests/fixtures/nosql-scenarios/scenarios.json +472 -0
- package/tests/fixtures/oci-maestro-routing/expected/031-happy-nosql-database-architect.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/032-happy-nosql-global-active-table.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/033-happy-nosql-pattern-recovery.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/034-happy-nosql-pattern-refactor.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-live-mutation.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-not-autonomous.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/031-happy-nosql-database-architect.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/032-happy-nosql-global-active-table.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/033-happy-nosql-pattern-recovery.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/034-happy-nosql-pattern-refactor.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-live-mutation.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-not-autonomous.json +7 -0
- package/tests/fixtures/oci-maestro-routing/taxonomy.json +27 -0
- package/tests/requirements-ci.txt +8 -0
- package/tests/validate-aws-skill-quality.py +7 -0
- package/tests/validate-nosql-audit.py +741 -0
- package/tests/validate-nosql-operations.py +136 -0
- package/tests/validate-nosql-pattern-evals.py +96 -0
- package/tests/validate-nosql-scenarios.py +94 -0
- package/tests/validate-skill-manifest.py +6 -1
- package/tests/validate-skill-references.py +225 -0
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
# Evidence index
|
|
2
|
+
|
|
3
|
+
This index maps the rows of [the evidence ledger](evidence-ledger.md) to the skill
|
|
4
|
+
files they support, and lists every claim that is unconfirmed or conflicting.
|
|
5
|
+
|
|
6
|
+
## Verification summary
|
|
7
|
+
|
|
8
|
+
Each material claim was checked against the provider page it cites, or the closest
|
|
9
|
+
official page, on 2026-11-09. No claim was contradicted. The orchestrator then re-checked every
|
|
10
|
+
VERIFIED quote mechanically on the cited page; rows it could not confirm were
|
|
11
|
+
downgraded to UNVERIFIED. UNVERIFIED and CONFLICT rows are listed below; treat those
|
|
12
|
+
statements as unconfirmed until re-checked.
|
|
13
|
+
|
|
14
|
+
## Evidence by topic
|
|
15
|
+
|
|
16
|
+
### Modeling, indexing, runtime contract, vectors, change feed and SDK adapters
|
|
17
|
+
|
|
18
|
+
Covers modeling.md, indexing-and-capacity.md, runtime-contract.md, data-types-and-vectors.md, embedding-integrations.md, change-feed-and-integrations.md, language-adapters.md, workflow.md, the design, refactor, performance-test, select and feature-plan commands and the runtime assets.
|
|
19
|
+
|
|
20
|
+
[CP-E101] [CP-E102] [CP-E103] [CP-E104] [CP-E105] [CP-E106] [CP-E107] [CP-E108]
|
|
21
|
+
[CP-E109] [CP-E110] [CP-E111] [CP-E112] [CP-E113] [CP-E114] [CP-E115] [CP-E116]
|
|
22
|
+
[CP-E117] [CP-E118] [CP-E119] [CP-E120] [CP-E121] [CP-E122] [CP-E123] [CP-E124]
|
|
23
|
+
[CP-E125] [CP-E126] [CP-E127] [CP-E128] [CP-E129] [CP-E130] [CP-E131] [CP-E132]
|
|
24
|
+
[CP-E133] [CP-E134] [CP-E135] [CP-E136] [CP-E137] [CP-E138] [CP-E139] [CP-E140]
|
|
25
|
+
[CP-E141] [CP-E142] [CP-E143] [CP-E144] [CP-E145] [CP-E146] [CP-E147] [CP-E148]
|
|
26
|
+
[CP-E149] [CP-E150] [CP-E151] [CP-E152] [CP-E153] [CP-E154] [CP-E155] [CP-E156]
|
|
27
|
+
[CP-E157] [CP-E158] [CP-E159] [CP-E160] [CP-E161] [CP-E162] [CP-E163] [CP-E164]
|
|
28
|
+
[CP-E165] [CP-E166] [CP-E167] [CP-E168] [CP-E169] [CP-E170] [CP-E171] [CP-E172]
|
|
29
|
+
[CP-E173] [CP-E174] [CP-E175] [CP-E176] [CP-E177] [CP-E178] [CP-E179] [CP-E180]
|
|
30
|
+
[CP-E181] [CP-E182] [CP-E183] [CP-E184] [CP-E185] [CP-E186] [CP-E187] [CP-E188]
|
|
31
|
+
[CP-E189] [CP-E190] [CP-E191]
|
|
32
|
+
|
|
33
|
+
### Access, encryption, monitoring, provisioning, recovery and replication
|
|
34
|
+
|
|
35
|
+
Covers access-control.md, encryption.md, monitoring.md, provisioning.md, recovery.md, replication.md, the Azure CLI, audit, backup, restore, recovery-target and help commands and the ARM and provisioning assets.
|
|
36
|
+
|
|
37
|
+
[CP-E301] [CP-E302] [CP-E303] [CP-E304] [CP-E305] [CP-E306] [CP-E307] [CP-E308]
|
|
38
|
+
[CP-E309] [CP-E310] [CP-E311] [CP-E312] [CP-E313] [CP-E314] [CP-E315] [CP-E316]
|
|
39
|
+
[CP-E317] [CP-E318] [CP-E319] [CP-E320] [CP-E321] [CP-E322] [CP-E323] [CP-E324]
|
|
40
|
+
[CP-E325] [CP-E326] [CP-E327] [CP-E328] [CP-E329] [CP-E330] [CP-E331] [CP-E332]
|
|
41
|
+
[CP-E333] [CP-E334] [CP-E335] [CP-E336] [CP-E337] [CP-E338] [CP-E339] [CP-E340]
|
|
42
|
+
[CP-E341] [CP-E342] [CP-E343] [CP-E344] [CP-E345] [CP-E346] [CP-E347] [CP-E348]
|
|
43
|
+
[CP-E349] [CP-E350] [CP-E351] [CP-E352] [CP-E353] [CP-E354] [CP-E355] [CP-E356]
|
|
44
|
+
[CP-E357] [CP-E358] [CP-E359] [CP-E360] [CP-E361] [CP-E362] [CP-E363] [CP-E364]
|
|
45
|
+
[CP-E365] [CP-E366] [CP-E367] [CP-E368]
|
|
46
|
+
|
|
47
|
+
## Unconfirmed and conflicting claims
|
|
48
|
+
|
|
49
|
+
| Evidence | Status | Claim |
|
|
50
|
+
| --- | --- | --- |
|
|
51
|
+
| [CP-E106] | UNVERIFIED | `id` is a string (references/modeling.md:3-4; data-types:8-9) |
|
|
52
|
+
| [CP-E124] | CONFLICT | ReadConsistencyStrategy is direct mode only (runtime-contract.md:6) |
|
|
53
|
+
| [CP-E125] | UNVERIFIED | Latest Committed / Global Strong offered by ReadConsistencyStrategy (runtime-contract.md:6) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
54
|
+
| [CP-E136] | UNVERIFIED | TTL relative to server `_ts` (runtime-contract.md:25) |
|
|
55
|
+
| [CP-E142] | UNVERIFIED | Not every Functions binding/processor has parity (all-versions-and-deletes) (change-feed.md:6) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
56
|
+
| [CP-E158] | CONFLICT | Vector policy/index mutability differs between pages (skill says docs vary) (data-types:27; feature-plan.md:10). Note: skill's "docs vary" statement is accurate |
|
|
57
|
+
| [CP-E161] | UNVERIFIED | If-Match used for conditional writes (replace/delete); patch via If-Match (runtime-contract.md:8; REST (language-adapters.md:94-95)). Note: patch part |
|
|
58
|
+
| [CP-E169] | UNVERIFIED | `response.headers?.["x-ms-session-token"]` read from a JS FeedResponse (assets/runtime.mjs:35). Note: likely returns undefined; see fix list |
|
|
59
|
+
| [CP-E170] | UNVERIFIED | `container.item(id, pk).replace(body, {accessCondition: {type: "IfMatch", condition: etag}})` (runtime.mjs:43-44). Note: shape ok, literal `"IfMatch"` unconfirmed |
|
|
60
|
+
| [CP-E172] | UNVERIFIED | 429 error carries `error.code` 429 and `error.headers["x-ms-retry-after-ms"]` in JS SDK (runtime.mjs:55). Note: JS error shape |
|
|
61
|
+
| [CP-E178] | UNVERIFIED | Java: CosmosQueryRequestOptions.setPartitionKey; container.queryItems(...).byPage(token, pageSize); CosmosItemRequestOptions.setIfMatchETag (language-adapters.md:39-46) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
62
|
+
| [CP-E179] | UNVERIFIED | No first-party NoSQL PHP SDK (language-adapters.md:14). Note: absence, consistent with skill's wording "not identified" Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
63
|
+
| [CP-E312] | UNVERIFIED | Key Vault must be publicly accessible or allow trusted-service bypass; private-endpoint-only vault not sufficient (references/encryption.md:27-30) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
64
|
+
| [CP-E317] | UNVERIFIED | Names, indexed paths and partition-key values are not all hidden by CMK (references/encryption.md:47-48) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
65
|
+
| [CP-E320] | UNVERIFIED | ARM API version 2025-04-15 exists for databaseAccounts, sqlDatabases, containers (references/provisioning.md:7; assets/account.arm.json:11,29,36) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
66
|
+
| [CP-E324] | CONFLICT | Account name 3-44 chars, lowercase letters/numbers/hyphens (assets/account.arm.json:5 (maxLength 44); assets/provision.sh:10) |
|
|
67
|
+
| [CP-E326] | UNVERIFIED | `az cosmosdb create` flags `--kind GlobalDocumentDB`, `--locations`, `--default-consistency-level`, `--backup-policy-type`, `--continuous-tier`, `--enable-automatic-failover`, `--enable-multiple-write-locations`, `--disable-local-auth`, `--public-network-access DISABLED`, `--minimal-tls-version Tls12` (assets/provision.sh:21-25) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
68
|
+
| [CP-E332] | UNVERIFIED | Strong consistency and multi-region writes not simultaneously supported (references/replication.md:6-7) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
69
|
+
| [CP-E340] | UNVERIFIED | Deleted container/database snapshots retained 30 days; shared-throughput backup/restore is database-scope (references/commands/backup/periodic.md:21-25) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
70
|
+
| [CP-E343] | UNVERIFIED | Tier change/migration shortens usable history; shorter tier loses older recovery points; new tier does not create older backups (references/commands/backup/continuous.md:9-10,13) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
71
|
+
| [CP-E352] | UNVERIFIED | Change feed restarts from beginning; only post-restore lifetime events; pre-deletion events not propagated (references/commands/restore/continuous-deleted-resource.md:42-45) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
72
|
+
| [CP-E355] | UNVERIFIED | `az cosmosdb restore` flags: `--account-name` (source), `--target-database-account-name`, `--location`, `--restore-timestamp`, `--resource-group`, `--disable-ttl`, `--disable-local-auth`, `--public-network-access DISABLED` (references/commands/restore/continuous-new-account.md:12-16) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. |
|
|
@@ -0,0 +1,174 @@
|
|
|
1
|
+
# Evidence ledger — Azure Cosmos DB for NoSQL patterns
|
|
2
|
+
|
|
3
|
+
Rows trace material provider claims in this skill to the official page that was
|
|
4
|
+
fetched and read on the retrieval date. [The evidence index](evidence-index.md) maps every
|
|
5
|
+
row to the skill files it covers; `tests/validate-skill-references.py` fails the build
|
|
6
|
+
if a citation has no row, a row is never cited, or a source is not an allow-listed
|
|
7
|
+
host.
|
|
8
|
+
|
|
9
|
+
`VERIFIED` = the cited section was retrieved and supports the claim as worded
|
|
10
|
+
(documentation verification, not a live cloud test). `UNVERIFIED` = no official
|
|
11
|
+
sentence settled it in this pass. `CONFLICT` = two official pages disagree. Limits and
|
|
12
|
+
APIs change: re-fetch before relying on a number.
|
|
13
|
+
|
|
14
|
+
| ID | Claim | Source | Section | Retrieved | Status |
|
|
15
|
+
| --- | --- | --- | --- | --- | --- |
|
|
16
|
+
| CP-E101 | Uniqueness is (partition key, id); point read needs id + partition key value (references/modeling.md:4-5) | https://learn.microsoft.com/azure/cosmos-db/partitioning-overview | Intro: "Combining the partition key and the item ID creates the item's index, which uniquely identifies the item." | 2026-11-09 | VERIFIED |
|
|
17
|
+
| CP-E102 | Logical partition max 20 GB; physical partition max 10,000 RU/s (references/modeling.md:17-18; runtime-contract (n/a)) | https://learn.microsoft.com/azure/cosmos-db/concepts-limits | Provisioned throughput: "Maximum RUs per partition (logical & physical) \ / 10,000"; "Maximum storage across all items per (logical) partition \ / 20 GB" | 2026-11-09 | VERIFIED |
|
|
18
|
+
| CP-E103 | Hierarchical partition keys up to three levels; prefix can span physical partitions (references/modeling.md:19-20) | https://learn.microsoft.com/azure/cosmos-db/hierarchical-partition-keys | Example use case: "The overall depth can't exceed three levels." and "it's possible for TenantId data to span multiple physical partitions." | 2026-11-09 | VERIFIED |
|
|
19
|
+
| CP-E104 | Partition key value immutable per item; changing configured key needs new container/copy (references/modeling.md:24-26) | https://learn.microsoft.com/azure/cosmos-db/partitioning-overview | Choose a partition key: "Once you select your partition key, you can't change it in place. If you need to change your partition key, move your data to a new container" | 2026-11-09 | VERIFIED |
|
|
20
|
+
| CP-E105 | Unique-key: scoped to logical partition, case-sensitive, no sparse uniqueness, missing treated as null; policy fixed at container creation (references/modeling.md:33-34) | https://learn.microsoft.com/azure/cosmos-db/unique-keys | Define a unique key: "Sparse unique keys aren't supported. If some unique path values are missing, they're treated as null values" ; "A unique key is scoped to a logical partition." | 2026-11-09 | VERIFIED |
|
|
21
|
+
| CP-E106 | `id` is a string (references/modeling.md:3-4; data-types:8-9) | https://learn.microsoft.com/azure/cosmos-db/hierarchical-partition-keys | Point read section: "The unique identifier for the item is a GUID. It's represented as a string" (concepts-limits gives ID length only; no explicit "id must be string" sentence found) | 2026-11-09 | UNVERIFIED |
|
|
22
|
+
| CP-E107 | Max item size 2 MB (references/data-types:9) | https://learn.microsoft.com/azure/cosmos-db/concepts-limits | Per-item limits: "Maximum size of an item \ / 2 MB (UTF-8 length of JSON representation)" | 2026-11-09 | VERIFIED |
|
|
23
|
+
| CP-E108 | Numbers are IEEE-754 double (precision loss for large ints/decimals) (references/data-types:6-7) | https://learn.microsoft.com/azure/cosmos-db/concepts-limits | Per-item limits: "Maximum length of numeric property value \ / IEEE754 double-precision 64-bit" | 2026-11-09 | VERIFIED |
|
|
24
|
+
| CP-E109 | Transactional batch: same partition key, container, <=100 ops, <=2 MB, <=5 s (references/runtime-contract.md:9; SKILL cross: workflow n/a) | https://learn.microsoft.com/azure/cosmos-db/transactional-batch | Limitations: "constrains the size of the transactional batch payload to not exceed 2 MB, and the maximum execution time is 5 seconds." and "limit of 100 operations per transactional batch" | 2026-11-09 | VERIFIED |
|
|
25
|
+
| CP-E110 | Stored procedures are partition-scoped (references/runtime-contract.md:9) | https://learn.microsoft.com/azure/cosmos-db/partitioning-overview | Choose a partition key: "All JavaScript-based stored procedures and triggers are scoped to a single logical partition." | 2026-11-09 | VERIFIED |
|
|
26
|
+
| CP-E111 | Default: every property indexed (range) with consistent indexing (references/indexing-and-capacity.md:3-4) | https://learn.microsoft.com/azure/cosmos-db/index-policy | Intro: "The default indexing policy for newly created containers indexes every property of every item and enforces range indexes for any string or number." | 2026-11-09 | VERIFIED |
|
|
27
|
+
| CP-E112 | ORDER BY multi-property needs matching composite index; same sequence/direction; reverse of all directions supported, mixed not (indexing-and-capacity.md:10; indexing-policy.json:6) | https://learn.microsoft.com/azure/cosmos-db/index-policy | Composite indexes: "The composite index also supports an ORDER BY clause with the opposite order on all paths." ; "Queries that have an ORDER BY clause with two or more properties require a composite index." | 2026-11-09 | VERIFIED |
|
|
28
|
+
| CP-E113 | compositeIndexes JSON shape with path + order "ascending"/"descending" (assets/indexing-policy.json:6) | https://learn.microsoft.com/azure/cosmos-db/index-policy | Composite indexes with an array wildcard: `"compositeIndexes":[ [ {"path":"/familyname", "order":"ascending"}, {"path":"/children/[]/age", "order":"descending"} ] ]` | 2026-11-09 | VERIFIED |
|
|
29
|
+
| CP-E114 | indexingMode consistent, automatic true, includedPaths /*, excludedPaths /_etag/? shapes (indexing-policy.json:2-5; vector-indexing-policy.json:2-5) | https://learn.microsoft.com/azure/cosmos-db/index-policy | Vector indexes (example): `"indexingMode": "consistent", "automatic": true, "includedPaths": [{"path": "/*"}], "excludedPaths": [{"path": "/_etag/?"}]` | 2026-11-09 | VERIFIED |
|
|
30
|
+
| CP-E115 | includedPaths/excludedPaths; more precise path takes precedence (indexing-and-capacity.md:13) | https://learn.microsoft.com/azure/cosmos-db/index-policy | Include/exclude precedence: "If your included paths and excluded paths have a conflict, the more precise path takes precedence." | 2026-11-09 | VERIFIED |
|
|
31
|
+
| CP-E116 | Index transformations are asynchronous; consume RUs (indexing-and-capacity.md:17-18) | https://learn.microsoft.com/azure/cosmos-db/index-policy | Modifying the indexing policy: "Index transformation is an asynchronous operation" ; "Index transformation is an operation that consumes request units." | 2026-11-09 | VERIFIED |
|
|
32
|
+
| CP-E117 | Manual throughput minimum 400 RU/s (indexing-and-capacity.md:21-22) | https://learn.microsoft.com/azure/cosmos-db/concepts-limits | Minimum throughput limits: "An Azure Cosmos DB container (or shared throughput database) using manual throughput must have a minimum throughput of 400 RU/s." | 2026-11-09 | VERIFIED |
|
|
33
|
+
| CP-E118 | Autoscale has configured max and dynamic minimum (indexing-and-capacity.md:22) | https://learn.microsoft.com/azure/cosmos-db/concepts-limits | Limits for autoscale provisioned throughput: "Minimum RU/s the system can scale to \ / 0.1 * Tmax" | 2026-11-09 | VERIFIED |
|
|
34
|
+
| CP-E119 | Database shared throughput vs per-container throughput are distinct (can be combined) (indexing-and-capacity.md:23-24) | https://learn.microsoft.com/azure/cosmos-db/set-throughput | Set throughput on a database and a container: "Provisioning throughput on both the database and the container is allowed." | 2026-11-09 | VERIFIED |
|
|
35
|
+
| CP-E120 | Serverless bills consumption (indexing-and-capacity.md:24-25) | https://learn.microsoft.com/azure/cosmos-db/concepts-limits | Serverless: "Serverless lets you use your Azure Cosmos DB resources in a consumption-based fashion." | 2026-11-09 | VERIFIED |
|
|
36
|
+
| CP-E121 | Five account consistency levels (Strong/BoundedStaleness/Session/ConsistentPrefix/Eventual) (runtime-contract.md:6) | https://learn.microsoft.com/azure/cosmos-db/consistency-levels | intro: "Azure Cosmos DB offers five well-defined levels. From strongest to weakest, the levels are: Strong, Bounded staleness, Session, Consistent prefix, Eventual" | 2026-11-09 | VERIFIED |
|
|
37
|
+
| CP-E122 | Traditional ConsistencyLevel override can weaken, not strengthen (runtime-contract.md:6) | https://learn.microsoft.com/azure/cosmos-db/how-to-manage-consistency | Override the default consistency level: "When using the traditional `ConsistencyLevel` override, consistency can only be **relaxed** at the SDK instance or request level." | 2026-11-09 | VERIFIED |
|
|
38
|
+
| CP-E123 | ReadConsistencyStrategy: preview, Java >=4.69 / .NET >=3.46 (runtime-contract.md:6) | https://learn.microsoft.com/azure/cosmos-db/how-to-manage-consistency | Use Read Consistency Strategy: "The `ReadConsistencyStrategy` feature (available in Java SDK v4.69+ and .NET SDK v3.46+)"; "`ReadConsistencyStrategy` is currently in **preview**." | 2026-11-09 | VERIFIED |
|
|
39
|
+
| CP-E124 | ReadConsistencyStrategy is direct mode only (runtime-contract.md:6) | https://learn.microsoft.com/azure/cosmos-db/how-to-manage-consistency | Use Read Consistency Strategy / Java API ref ReadConsistencyStrategy Enum: how-to: "It's supported in **direct mode only** and isn't available when using gateway mode." Java API ref: "NOTE: The ReadConsistencyStrategy is honored across all connection modes." (.NET ref: "The strategy is honored | 2026-11-09 | CONFLICT |
|
|
40
|
+
| CP-E125 | Latest Committed / Global Strong offered by ReadConsistencyStrategy (runtime-contract.md:6) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/how-to-manage-consistency | Available strategies: "Available strategies \ / ... Default, Session, Eventual, Latest Committed, Global Strong" ; .NET ref: "GlobalStrong ... Only valid for accounts configured with Strong consistency." | 2026-11-09 | UNVERIFIED |
|
|
41
|
+
| CP-E126 | Strong account consistency isn't multi-write-compatible (runtime-contract.md:6) | https://learn.microsoft.com/azure/cosmos-db/consistency-levels | Strong consistency and multiple write regions: "Azure Cosmos DB accounts with multiple write regions can't use strong consistency" | 2026-11-09 | VERIFIED |
|
|
42
|
+
| CP-E127 | Session tokens are partition-bound, opaque; transfer token across stateless clients; SDK tracks token automatically (runtime-contract.md:7) | https://learn.microsoft.com/azure/cosmos-db/consistency-levels | Session consistency: "Session Tokens in Azure Cosmos DB are partition-bound, meaning they're exclusively associated with one partition." ; "If Session Tokens are being passed from one client instance to another, the contents of the token sho | 2026-11-09 | VERIFIED |
|
|
43
|
+
| CP-E128 | Optimistic concurrency via _etag + If-Match; stale -> 412 (runtime-contract.md:8) | https://learn.microsoft.com/azure/cosmos-db/database-transactions-optimistic-concurrency | Implement optimistic concurrency control using ETag and HTTP headers: "If the value of the `if-match` request header is no longer current, the server rejects the operation with an "HTTP 412 Precondition failure" response message." | 2026-11-09 | VERIFIED |
|
|
44
|
+
| CP-E129 | Create of existing id returns 409 (runtime-contract.md:8) | https://learn.microsoft.com/azure/cosmos-db/transactional-batch | How to create a transactional batch operation (Important note): "If the operation fails because it tries to create an item that already exists, a status code of 409 (conflict) is returned." | 2026-11-09 | VERIFIED |
|
|
45
|
+
| CP-E130 | Bulk/cross-partition queries aren't ACID transactions; ACID scope is logical partition (runtime-contract.md:9) | https://learn.microsoft.com/azure/cosmos-db/transactional-batch | What's a transaction: "Azure Cosmos DB supports full ACID compliant transactions with snapshot isolation for operations within the same logical partition key." | 2026-11-09 | VERIFIED |
|
|
46
|
+
| CP-E131 | Continuation token is opaque; empty page possible; keep same query/SDK context; tokens valid with same SDK version (runtime-contract.md:10) | https://learn.microsoft.com/cosmos-db/query/pagination | Query executions / Continuation tokens: "In some cases, it's also possible that your query could return an empty page of results." ; "As long as you're using the same SDK version, continuation tokens never expire." | 2026-11-09 | VERIFIED |
|
|
47
|
+
| CP-E132 | GROUP BY / DISTINCT no continuation (DISTINCT ok with ORDER BY); Python aggregate cross-partition no continuation, streamable ok (runtime-contract.md:11; language-adapters.md:15) | https://learn.microsoft.com/cosmos-db/query/pagination | Continuation tokens: "Aggregate cross-partition queries (sorting, counting, distinct) do not support continuation tokens." ; "You can't use continuation tokens for queries with GROUP BY or DISTINCT ... For queries with DISTINCT, you can use | 2026-11-09 | VERIFIED |
|
|
48
|
+
| CP-E133 | SDK retries 429 by default and honors x-ms-retry-after-ms (runtime-contract.md:12) | https://learn.microsoft.com/azure/cosmos-db/conceptual-resilient-sdk-applications | HTTP 429: "The Azure Cosmos DB SDKs retry on HTTP 429 errors by default following the client configuration and honoring the service's response `x-ms-retry-after-ms` header" | 2026-11-09 | VERIFIED |
|
|
49
|
+
| CP-E134 | Timeout/connectivity on writes: SDK does not retry; unknown outcome (runtime-contract.md:13) | https://learn.microsoft.com/azure/cosmos-db/conceptual-resilient-sdk-applications | Timeouts and connectivity related failures (HTTP 408/503): "For write operations, the SDKs do *not* retry because these operations are *not idempotent*." | 2026-11-09 | VERIFIED |
|
|
50
|
+
| CP-E135 | TTL: null/absent off; -1 default no expiry; positive = seconds; item ttl -1 opt out; item ttl only effective when container TTL enabled; relative to last modified (runtime-contract.md:23-26) | https://learn.microsoft.com/azure/cosmos-db/time-to-live | Time to live for containers and items: "If missing (or set to null), items aren't expired automatically."; "If present, and the value is set to "-1," it's equal to infinity, and items don't expire by default."; "interpreted as a delta from the time that an it | 2026-11-09 | VERIFIED |
|
|
51
|
+
| CP-E136 | TTL relative to server `_ts` (runtime-contract.md:25) | https://learn.microsoft.com/azure/cosmos-db/time-to-live | Intro: Page says only "since the time they were last modified"; the string `_ts` does not appear on the page (index-policy page only lists `_ts` as a system property always indexed). | 2026-11-09 | UNVERIFIED |
|
|
52
|
+
| CP-E137 | Expired items stop appearing in queries; physical deletion asynchronous, uses available RUs, not a deadline SLA (runtime-contract.md:26-28) | https://learn.microsoft.com/azure/cosmos-db/time-to-live | intro: "An item no longer appears in query responses immediately after the TTL expires, even if it's not yet permanently deleted"; "If the container doesn't have enough request units (RUs) to perform the deletion, the data dele | 2026-11-09 | VERIFIED |
|
|
53
|
+
| CP-E138 | Restore replays container TTL config; restore has disable-TTL option (runtime-contract.md:26-30; feature-plan.md:9) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction | Time to live: "The default restore process restores all the properties of a container including its TTL configuration by default. This can result in deletion of data if restore is done without disabling the TTL." (--disable-ttl / -Dis | 2026-11-09 | VERIFIED |
|
|
54
|
+
| CP-E139 | Latest-version mode: creates/updates only, coalesced to latest version, deletes not captured (so TTL deletions missing) (change-feed.md:5; runtime-contract.md:35-36; refactor.md:11) | https://learn.microsoft.com/azure/cosmos-db/change-feed-modes | Latest version change feed mode: "if an item is created and then updated before you read the change feed, only the updated version appears in the change feed. Deletes aren't captured as changes" | 2026-11-09 | VERIFIED |
|
|
55
|
+
| CP-E140 | Latest version mode is the default (change-feed.md:5) | https://learn.microsoft.com/azure/cosmos-db/change-feed-modes | Latest version change feed mode: "Latest version change feed mode is enabled by default" | 2026-11-09 | VERIFIED |
|
|
56
|
+
| CP-E141 | All versions and deletes: NoSQL-only, requires continuous backup, history bounded by continuous-backup retention (change-feed.md:6) | https://learn.microsoft.com/azure/cosmos-db/change-feed-modes | All versions and deletes change feed mode: "you must have continuous backups configured for your Azure Cosmos DB account... You can only read changes that occurred within the continuous backup period... only compatible with Azure Cosmos DB for NoSQL accounts." | 2026-11-09 | VERIFIED |
|
|
57
|
+
| CP-E142 | Not every Functions binding/processor has parity (all-versions-and-deletes) (change-feed.md:6) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/change-feed-modes | Work with the change feed (all versions and deletes tab): Table: Change feed processor .NET >=3.60.0, Java >=4.81.0, Python No, Node.js No; "Azure Functions trigger" .NET isolated worker >= 4.16.1, Java No, Python No, Node.js No | 2026-11-09 | UNVERIFIED |
|
|
58
|
+
| CP-E143 | Processor: lease container for checkpoint/state, at-least-once, rebalance across instances (change-feed.md:11-12) | https://learn.microsoft.com/azure/cosmos-db/change-feed-processor | intro / Components: "The main benefit of the change feed processor is its fault-tolerant design, which assures an at-least-once delivery of all the events in the change feed." | 2026-11-09 | VERIFIED |
|
|
59
|
+
| CP-E144 | Per-partition ordering only; no global total ordering (change-feed.md:12) | https://learn.microsoft.com/azure/cosmos-db/change-feed | Sort order of items in change feed: "This sort order is guaranteed per partition key, and there's no guaranteed order across the partition key values." | 2026-11-09 | VERIFIED |
|
|
60
|
+
| CP-E145 | Consumer data/lease RBAC distinct from app read RBAC (readChangeFeed on monitored; items/create,replace,delete,read,executeQuery on lease) (change-feed.md:13) | https://learn.microsoft.com/azure/cosmos-db/change-feed-processor | Role-based access requirements: "On the monitored container: ...sqlDatabases/containers/readChangeFeed"; "On the lease container: ...items/read ... items/create ... items/replace ... items/delete ... items/executeQuery" | 2026-11-09 | VERIFIED |
|
|
61
|
+
| CP-E146 | Same-account deleted-resource restore: new resource; session/continuation tokens invalid; restart clients; restart feed from beginning; pre-deletion feed events not propagated (change-feed.md:15-21) | https://learn.microsoft.com/azure/cosmos-db/restore-in-account-continuous-backup-introduction | What is restored? (Note): "those resource should be treated as new resources. Existing session or continuation tokens ... become invalid." ; "it should restart the change feed from the beginning after a restore operation... All change feed events | 2026-11-09 | VERIFIED |
|
|
62
|
+
| CP-E147 | Latest-version deletion pattern: soft-delete marker + TTL; consumers must process before TTL expiry (change-feed.md:25-26) | https://learn.microsoft.com/azure/cosmos-db/change-feed-modes | Features of each mode (latest version): "you have to process the changes within a shorter time interval than the TTL expiration period." | 2026-11-09 | VERIFIED |
|
|
63
|
+
| CP-E148 | Vector dataType in ARM 2025-04-15 enum is float32/int8/uint8 only (data-types:21; assets/vector-policy.json:2; runtime.mjs:67) | https://learn.microsoft.com/azure/templates/microsoft.documentdb/2025-04-15/databaseaccounts/sqldatabases/containers | VectorEmbedding: "dataType \ / Indicates the data type of vector. \ / 'float32''int8''uint8' (required)" | 2026-11-09 | VERIFIED |
|
|
64
|
+
| CP-E149 | Current vector page supports float32, float16, int8, uint8 (data-types:21; vector-policy.json) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Container vector policies: "`datatype`: The data type of the vector property. Supported types are `float32`, `float16`, `int8`, and `uint8`." | 2026-11-09 | VERIFIED |
|
|
65
|
+
| CP-E150 | NoSQL supports native vector indexing and VectorDistance; query shape SELECT TOP .. ORDER BY VectorDistance (data-types:13-15) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Perform vector search with queries using VectorDistance: "SELECT TOP 10 c.title, VectorDistance(c.contentVector, [1,2,3]) AS SimilarityScore FROM c ORDER BY VectorDistance(c.contentVector, [1,2,3])" ; "Always use a `TOP N` clause" | 2026-11-09 | VERIFIED |
|
|
66
|
+
| CP-E151 | Vector embedding policy has path/dataType/dimensions/distanceFunction; vector index policy `vectorIndexes` [{path,type}] on same path; policy JSON top-level `vectorEmbeddings` (data-types:15-17; vector-policy.json:2; vector-indexing-policy.json:6) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Container vector policies / Vector indexing policies: `{"vectorEmbeddings": [{"path":"/vector1","dataType":"float32","distanceFunction":"cosine","dimensions":1536}]}` ; `"vectorIndexes": [{"path": "/vector1","type": "diskANN"}]` ; "A vector indexing policy must be on the pa | 2026-11-09 | VERIFIED |
|
|
67
|
+
| CP-E152 | Nested array / wildcard vector paths unsupported (data-types:17-18) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Vector indexing policies: "Wild card characters (`*`, `[]`) and vector paths nested inside arrays aren't currently supported in the vector policy or vector index." | 2026-11-09 | VERIFIED |
|
|
68
|
+
| CP-E153 | Dimensions: flat max 505; quantizedFlat/diskANN max 4096 (data-types:23) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Current limitations: "Vectors indexed with the `flat` index type can be at most 505 dimensions. Vectors indexed with the `quantizedFlat` or `DiskANN` index type can be at most 4,096 dimensions." | 2026-11-09 | VERIFIED |
|
|
69
|
+
| CP-E154 | Distance functions cosine, dotproduct, euclidean (data-types:24) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Container vector policies: "Supported metrics are: cosine (default)... dot product ... euclidean" ; JSON value `"dotproduct"` in two-path example | 2026-11-09 | VERIFIED |
|
|
70
|
+
| CP-E155 | flat = exact brute force; quantizedFlat quantized brute force; diskANN approximate; last two need >=1000 vectors else full scan (data-types:25) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Vector indexing policies (Note): "The `quantizedFlat` and `diskANN` indexes require that at least 1,000 vectors are inserted... If there are fewer than 1,000 vectors, a full scan is executed instead." | 2026-11-09 | VERIFIED |
|
|
71
|
+
| CP-E156 | Vector search not supported on shared-throughput accounts; use dedicated container throughput (data-types:26; indexing-and-capacity n/a) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Current limitations: "At this time, vector indexing and search aren't supported on accounts with Shared Throughput." | 2026-11-09 | VERIFIED |
|
|
72
|
+
| CP-E157 | Cannot disable vector indexing once enabled (data-types:27; feature-plan.md:10) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Current limitations: "Once vector indexing and search are enabled on a container, it can't be disabled." | 2026-11-09 | VERIFIED |
|
|
73
|
+
| CP-E158 | Vector policy/index mutability differs between pages (skill says docs vary) (data-types:27; feature-plan.md:10). Note: skill's "docs vary" statement is accurate | https://learn.microsoft.com/azure/cosmos-db/index-policy | Vector indexes (index-policy) vs Vector indexing policies (vector-search): index-policy: "Currently, vector policies and vector indexes are immutable after creation. To make changes, please create a new collection." vector-search: "You can add new path configurations or remove existing ones, bu | 2026-11-09 | CONFLICT |
|
|
74
|
+
| CP-E159 | Account capability name `EnableNoSQLVectorSearch` via az cosmosdb update --capabilities (data-types:33; embedding-integrations n/a) | https://learn.microsoft.com/azure/cosmos-db/nosql/vector-search | Enable the vector indexing and search feature: "az cosmosdb update --resource-group <resource-group-name> --name <account-name> --capabilities EnableNoSQLVectorSearch" ; "it might take 15 minutes to take effect" | 2026-11-09 | VERIFIED |
|
|
75
|
+
| CP-E160 | JSON types string/number/boolean/null/array/object; numbers IEEE 754 binary64 (data-types:6-9; modeling.md:3) | https://learn.microsoft.com/azure/cosmos-db/concepts-limits | Per-item limits: "Maximum precision/range for numbers in JSON (to ensure safe interoperability) \ / IEEE 754 binary64" | 2026-11-09 | VERIFIED |
|
|
76
|
+
| CP-E161 | If-Match used for conditional writes (replace/delete); patch via If-Match (runtime-contract.md:8; REST (language-adapters.md:94-95)). Note: patch part | https://learn.microsoft.com/rest/api/cosmos-db/common-cosmosdb-rest-request-headers | Common Azure Cosmos DB REST request headers: "If-Match \ / Optional (applicable only on PUT and DELETE)"; Patch Document REST page lists no If-Match header. PUT/DELETE covered; "patch ... using If-Match" not documented for REST. | 2026-11-09 | UNVERIFIED |
|
|
77
|
+
| CP-E162 | REST Entra authorization value is URL-encoded `type=aad&ver=1.0&sig=<token>` (language-adapters.md:70-72) | https://learn.microsoft.com/rest/api/cosmos-db/access-control-on-cosmosdb-resources | Authorization header: "{typeoftoken} denotes the type of token: master, resource, or aad (if you are using Azure Cosmos DB RBAC)." ; "The authorization string should be encoded before adding it to the REST request" | 2026-11-09 | VERIFIED |
|
|
78
|
+
| CP-E163 | REST query: POST /dbs/{db}/colls/{coll}/docs; headers x-ms-documentdb-isquery True, Content-Type application/query+json, x-ms-max-item-count, x-ms-continuation, body {query, parameters:[{name,value}]} (language-adapters.md:73,82-88) | https://learn.microsoft.com/rest/api/cosmos-db/query-documents | Request / Headers / Body: "x-ms-documentdb-isquery ... Must be set to True"; "Content-Type ... must be set to application/query+json"; body `{"query": ..., "parameters": [{"name": "@id","value": ...}]}` | 2026-11-09 | VERIFIED |
|
|
79
|
+
| CP-E164 | `x-ms-documentdb-partitionkey` header is JSON array of the key value (language-adapters.md:85) | https://learn.microsoft.com/rest/api/cosmos-db/common-cosmosdb-rest-request-headers | Common request headers: "x-ms-documentdb-partitionkey \ / Optional \ / Array \ / The partition key value ... this is an array containing just one value." | 2026-11-09 | VERIFIED |
|
|
80
|
+
| CP-E165 | x-ms-version 2018-12-31; x-ms-date RFC 1123 UTC format (language-adapters.md:82-83) | https://learn.microsoft.com/rest/api/cosmos-db/access-control-on-cosmosdb-resources | Constructing the hashed token signature (sample): `httpClient.DefaultRequestHeaders.Add("x-ms-version", "2018-12-31");` ; common headers: "x-ms-date ... RFC 1123 date format expressed in Coordinated Universal Time, for example, Fri, 08 Apr 2015 03:52:31 GMT" | 2026-11-09 | VERIFIED |
|
|
81
|
+
| CP-E166 | Session token header `x-ms-session-token`; response gives x-ms-request-charge, x-ms-activity-id (language-adapters.md:89-90; runtime.mjs:35) | https://learn.microsoft.com/rest/api/cosmos-db/query-documents | Response headers: "x-ms-request-charge \ / Number \ / The number of request units consumed by the operation." ; session token header listed under request headers | 2026-11-09 | VERIFIED |
|
|
82
|
+
| CP-E167 | JS FeedOptions accepts partitionKey, maxItemCount, continuationToken, sessionToken (language-adapters.md:11 / runtime.mjs:18-24) | https://learn.microsoft.com/javascript/api/@azure/cosmos/feedoptions | Properties: "continuationToken: Opaque token for continuing the enumeration." ; "maxItemCount: Max number of items to be returned in the enumeration operation." ; "partitionKey: Limits the query to a specific partition key." ; "sess | 2026-11-09 | VERIFIED |
|
|
83
|
+
| CP-E168 | FeedResponse exposes resources, requestCharge, continuationToken, activityId (runtime.mjs:24-36) | https://learn.microsoft.com/javascript/api/@azure/cosmos/feedresponse | Properties: Property list: "activityId, continuation, continuationToken, correlatedActivityId, diagnostics, hasMoreResults, indexMetrics, queryMetrics, requestCharge, resources" | 2026-11-09 | VERIFIED |
|
|
84
|
+
| CP-E169 | `response.headers?.["x-ms-session-token"]` read from a JS FeedResponse (assets/runtime.mjs:35). Note: likely returns undefined; see fix list | https://learn.microsoft.com/javascript/api/@azure/cosmos/feedresponse | Properties: FeedResponse documented properties (see CP-E168) do not include `headers`; headers is only a constructor parameter "headers: CosmosHeaders". No documented way to read the session token from FeedResponse | 2026-11-09 | UNVERIFIED |
|
|
85
|
+
| CP-E170 | `container.item(id, pk).replace(body, {accessCondition: {type: "IfMatch", condition: etag}})` (runtime.mjs:43-44). Note: shape ok, literal `"IfMatch"` unconfirmed | https://learn.microsoft.com/javascript/api/@azure/cosmos/requestoptions | accessCondition: `accessCondition?: { condition: string, type: string }` (the literal value "IfMatch" for `type` is not stated on the page) | 2026-11-09 | UNVERIFIED |
|
|
86
|
+
| CP-E171 | JS `container.items.batch(operations, partitionKey)` with `{operationType:"Create", resourceBody}`; limit 100 (language-adapters.md:29-32) | https://learn.microsoft.com/javascript/api/@azure/cosmos/items | batch(OperationInput[], PartitionKey, RequestOptions): "function batch(operations: OperationInput[], partitionKey?: PartitionKey, options?: RequestOptions)"; `operationType: "Create", resourceBody: {...}` ; "List of operations. Limit 100" | 2026-11-09 | VERIFIED |
|
|
87
|
+
| CP-E172 | 429 error carries `error.code` 429 and `error.headers["x-ms-retry-after-ms"]` in JS SDK (runtime.mjs:55). Note: JS error shape | https://learn.microsoft.com/azure/cosmos-db/conceptual-resilient-sdk-applications | HTTP 429: Page documents header `x-ms-retry-after-ms` on 429 responses; the JS ErrorResponse `code` / `headers` property names were not found on a fetched page | 2026-11-09 | UNVERIFIED |
|
|
88
|
+
| CP-E173 | JS `new CosmosClient({endpoint, aadCredentials: credential})` for Entra (language-adapters.md:24) | https://learn.microsoft.com/javascript/api/@azure/cosmos/cosmosclientoptions | Properties: "aadCredentials \ / AAD token from `@azure/identity`" (`aadCredentials?: TokenCredential`) | 2026-11-09 | VERIFIED |
|
|
89
|
+
| CP-E174 | The Python SDK queries with `container.query_items(...)` and takes a `partition_key` argument; `query_iterable` is only a sample variable name, not an SDK method (language-adapters.md:15, corrected) | https://learn.microsoft.com/azure/cosmos-db/performance-tips-query-sdk | Reduce query plan calls: "For single partition queries, specify the partition key value for the item and pass it as" | 2026-11-09 | VERIFIED |
|
|
90
|
+
| CP-E175 | Rust `azure_data_cosmos` + `azure_identity` public preview, no SLA, not recommended for production (language-adapters.md:13) | https://learn.microsoft.com/azure/cosmos-db/quickstart-rust | intro: "The Rust SDK for Azure Cosmos DB is currently in public preview. This preview is provided without a service-level agreement, and we don't recommend it for production workloads." | 2026-11-09 | VERIFIED |
|
|
91
|
+
| CP-E176 | Rust `container.read_item(pk, id, None)`; `query_items::<T>(Query::from(..).with_parameter(..)?, pk, None)` (language-adapters.md:61-65) | https://learn.microsoft.com/azure/cosmos-db/quickstart-rust | Read an item / Query items: `container.read_item(item_partition_key, item_id, None).await?` ; `Query::from("SELECT * FROM c WHERE c.category = @category").with_parameter("@category", item_partition_key)?` ; `container.query_items::<Item>(query, ite | 2026-11-09 | VERIFIED |
|
|
92
|
+
| CP-E177 | Go `github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos`; pager (language-adapters.md:17) | https://learn.microsoft.com/azure/cosmos-db/quickstart-go | Install the client library / Query items: "go install github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos" ; "container.NewQueryItemsPager" | 2026-11-09 | VERIFIED |
|
|
93
|
+
| CP-E178 | Java: CosmosQueryRequestOptions.setPartitionKey; container.queryItems(...).byPage(token, pageSize); CosmosItemRequestOptions.setIfMatchETag (language-adapters.md:39-46) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/java/api/com.azure.cosmos.util.cosmospagedflux | Method Details byPage: "byPage(String continuationToken, int preferredPageSize) Gets a Flux of FeedResponse<T> beginning at the page identified by the given continuation token requesting each page to contain the number of elements equal to the | 2026-11-09 | UNVERIFIED |
|
|
94
|
+
| CP-E179 | No first-party NoSQL PHP SDK (language-adapters.md:14). Note: absence, consistent with skill's wording "not identified" Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/overview | SDK list: "Software Development Kits (SDKs) are available for popular programming languages, including .NET, Python, TypeScript, JavaScript, Java, Go, and Rust." (PHP not listed; PHP appears only for Table/Storage SDKs) | 2026-11-09 | UNVERIFIED |
|
|
95
|
+
| CP-E180 | A SQL query with an id predicate is not a point read (modeling.md:5-6; indexing-and-capacity.md:16) | https://learn.microsoft.com/azure/cosmos-db/optimize-cost-reads-writes | Read data: point reads and queries: "Queries that filter on one item's ID and partition key aren't considered a point read." | 2026-11-09 | VERIFIED |
|
|
96
|
+
| CP-E181 | RU depends on item size, indexes, query shape, consistency (strong/bounded ~2x read RU) (indexing-and-capacity.md:20-21) | https://learn.microsoft.com/azure/cosmos-db/request-units | Request Unit considerations: "Data consistency: The strong and bounded staleness consistency levels consume approximately two times more RUs while performing read operations" | 2026-11-09 | VERIFIED |
|
|
97
|
+
| CP-E182 | Never set manual throughput and autoscale max simultaneously (indexing-and-capacity.md:24-25) | https://learn.microsoft.com/azure/templates/microsoft.documentdb/2025-04-15/databaseaccounts/sqldatabases/containers | CreateUpdateOptions: "Specifies the Autoscale settings. Note: Either throughput or autoscaleSettings is required, but not both." | 2026-11-09 | VERIFIED |
|
|
98
|
+
| CP-E183 | `SELECT TOP @k` parameterized (data-types.md:38; assets) | https://learn.microsoft.com/cosmos-db/query/parameterized-queries | Examples: `"query": "SELECT TOP @pageSize * FROM products"` with `"parameters": [{"name": "@pageSize","value": 10}]` | 2026-11-09 | VERIFIED |
|
|
99
|
+
| CP-E184 | Backup always present (periodic default or continuous); continuous -> periodic unsupported (feature-plan.md:14-15) | https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore | Backup modes / FAQ: "If your account is configured in continuous mode, you can't switch it back to periodic mode." ; "All Azure Cosmos DB accounts always have automatic backups." ; "Accounts use periodic backup mode by default" | 2026-11-09 | VERIFIED |
|
|
100
|
+
| CP-E185 | Encryption at rest isn't an on/off feature (feature-plan.md:15) | https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest | intro: "encryption at rest is "on" by default. There are no controls to turn it off or on." | 2026-11-09 | VERIFIED |
|
|
101
|
+
| CP-E186 | text-embedding-3-small/large support `dimensions` and `encoding_format` ("float"); default dims depend on model (small 1536, large 3072) (embedding-integrations.md:17-19,28-30) | https://learn.microsoft.com/rest/api/microsoft-foundry/azureopenai/embeddings | Create embedding: "dimensions ... Only supported in `text-embedding-3` and later models."; "encoding_format ... `float` or `base64` ... default float"; models page: text-embedding-3-large 3,072 / text-embedding-3-small 1,536 output dimens | 2026-11-09 | VERIFIED |
|
|
102
|
+
| CP-E187 | Azure OpenAI "v1-compatible" endpoint usable with `openai` client (embedding-integrations.md:23-24) | https://learn.microsoft.com/rest/api/microsoft-foundry/azureopenai/embeddings | Create embedding: "POST {endpoint}/openai/v1/embeddings" with endpoint "https://YOUR-RESOURCE-NAME.openai.azure.com/openai/v1/" | 2026-11-09 | VERIFIED |
|
|
103
|
+
| CP-E188 | Point read needs id + full partition key value (HPK: all levels); prefix queries are routed but middle-only is cross-partition (modeling.md:4-5; 19-20) | https://learn.microsoft.com/azure/cosmos-db/hierarchical-partition-keys | Perform a key/value lookup (point read) / Run a query: "To perform a point read on a single item, pass in the `id` property of the item and the full value for the partition key, including all three components of the path." ; "Queries that provide only the "middle" of the hie | 2026-11-09 | VERIFIED |
|
|
104
|
+
| CP-E189 | Partition key value can be string or numeric (typed key) (modeling.md:4-5; runtime-contract.md:5) | https://learn.microsoft.com/azure/cosmos-db/partitioning-overview | Choose a partition key: "The partition key value can be of string or numeric types." | 2026-11-09 | VERIFIED |
|
|
105
|
+
| CP-E190 | Recreated client loses session-token cache (reads behave like eventual until writes rebuild) (runtime-contract.md:7) | https://learn.microsoft.com/azure/cosmos-db/consistency-levels | Session consistency: "if the client is re-created, its cache of session tokens is also re-created. Here too, read operations follow the same behavior as Eventual Consistency" | 2026-11-09 | VERIFIED |
|
|
106
|
+
| CP-E191 | Containers default to consistent indexing; consistent mode index updated synchronously (indexing-and-capacity.md:3-4) | https://learn.microsoft.com/azure/cosmos-db/index-policy | Indexing mode: "Consistent: The index is updated synchronously as you create, update, or delete items." | 2026-11-09 | VERIFIED |
|
|
107
|
+
| CP-E301 | Data Reader built-in role ID ends 0...0001; Data Contributor ends 0...0002 (references/access-control.md:12) | https://learn.microsoft.com/azure/cosmos-db/reference-data-plane-security | Built-in roles: "Cosmos DB Built-in Data Reader **ID**: `00000000-0000-0000-0000-000000000001`" / "Cosmos DB Built-in Data Contributor **ID**: `00000000-0000-0000-0000-000000000002`" | 2026-11-09 | VERIFIED |
|
|
108
|
+
| CP-E302 | NoSQL data plane uses Cosmos SQL role definitions/assignments with dataActions; scope account `/`, db `/dbs/<db>`, container `/dbs/<db>/colls/<container>` (references/access-control.md:6,25) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-rbac | Grant data plane role-based access (step 5 and scope tips): "To grant access to the entire account, use `/` as the scope." Also: "you can scope the assignment to a single container, the most granular scope" (path `.../dbs/<database-name>/colls/<container-name>`) | 2026-11-09 | VERIFIED |
|
|
109
|
+
| CP-E303 | Query / change-feed access needs executeQuery, readChangeFeed and readMetadata data actions; native RBAC lists exact actions (custom roles) (references/access-control.md:13-15) | https://learn.microsoft.com/azure/cosmos-db/reference-data-plane-security | Built-in actions: "To perform NoSQL queries using the software development kits (SDKs), you must have both the `.../containers/executeQuery` and `.../containers/readChangeFeed` permissions." Also: "This action [readMetadata] must be allow | 2026-11-09 | VERIFIED |
|
|
110
|
+
| CP-E304 | `az cosmosdb sql role assignment create` flags `--principal-id`, `--role-definition-id`, `--scope`, `--account-name`; principal is an object ID (references/access-control.md:21-25,28) | https://learn.microsoft.com/cli/azure/cosmosdb/sql/role/assignment?view=azure-cli-latest | az cosmosdb sql role assignment create: "--principal-id -p AAD Object ID of the principal to which this Role Assignment is being granted." and "--role-definition-id -d Unique ID of the Role Definition that this Role Assignment refers to." | 2026-11-09 | VERIFIED |
|
|
111
|
+
| CP-E305 | Azure RBAC Contributor/Operator controls account configuration, not NoSQL item access; control-plane access needed to manage native data RBAC definitions (references/access-control.md:5,9) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-rbac | Grant control plane role-based access: Cosmos DB Operator role description: "Lets you manage Azure Cosmos DB accounts, but not access data in them. Prevents access to account keys and connection strings." (Contributor role not separately quoted on the page; O | 2026-11-09 | VERIFIED |
|
|
112
|
+
| CP-E306 | Restore needs `Microsoft.DocumentDB/locations/restorableDatabaseAccounts/read` and restore actions plus permission to create destination resources; a data-plane assignment alone cannot restore (references/access-control.md:34-38) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-permissions | Permissions on the source account / Permissions on the destination account: "`Microsoft.DocumentDB/locations/restorableDatabaseAccounts/restore/action` ... required on the source restorable database account scope to allow restore actions" and "`Microsoft.DocumentDB/databaseAccounts/write` This p | 2026-11-09 | VERIFIED |
|
|
113
|
+
| CP-E307 | At-rest encryption is always enabled; omitting key URI = service-managed keys, not plaintext (references/encryption.md:3,47-48) | https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest | Data encryption in Azure Cosmos DB (intro): "encryption at rest is \"on\" by default. There are no controls to turn it off or on." | 2026-11-09 | VERIFIED |
|
|
114
|
+
| CP-E308 | CMK is an extra encryption layer on top of service-managed keys (references/encryption.md:8,50) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | Intro / Customer-managed keys and double encryption: "Optionally, you can choose to add a second layer of encryption with keys you manage (*customer-managed keys* or CMK)." | 2026-11-09 | VERIFIED |
|
|
115
|
+
| CP-E309 | CMK account: identity.type UserAssigned + userAssignedIdentities, properties.defaultIdentity `UserAssignedIdentity=<id>`, properties.keyVaultKeyUri; CLI `--assign-identity`, `--default-identity "UserAssignedIdentity=..."`, `--key-uri` (references/encryption.md:15-22) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | Using a managed identity in the Azure Key Vault access policy: `"identity": {"type": "UserAssigned", "userAssignedIdentities": {"<identity-resource-id>": {}}}` ... `"defaultIdentity": "UserAssignedIdentity=<identity-resource-id>", "keyVaultKeyUri": "<key-vault-key-uri>"`; CLI: `--ke | 2026-11-09 | VERIFIED |
|
|
116
|
+
| CP-E310 | Versionless key URI supported for rotation flow (references/encryption.md:18-19) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | Generate a key in Azure Key Vault; Key rotation: "Copy the key's **Key Identifier**, except the part after the last forward slash" and "Key autorotation in Azure Key Vault is supported as long as the previous key isn't disabled or deleted." | 2026-11-09 | VERIFIED |
|
|
117
|
+
| CP-E311 | Key Vault needs soft delete AND purge protection; permissions Get/Wrap Key/Unwrap Key or RBAC role Key Vault Crypto Service Encryption User (references/encryption.md:24-27) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | Configure your Azure Key Vault instance; Add an access policy; Add role-based access control roles: "requires you to set two properties on the Azure Key Vault instance ...: **Soft Delete** and **Purge Protection**." / "select **Get**, **Unwrap Key**, and **Wrap Key** permissions" / "look for the **Key Vault Crypto Serv | 2026-11-09 | VERIFIED |
|
|
118
|
+
| CP-E312 | Key Vault must be publicly accessible or allow trusted-service bypass; private-endpoint-only vault not sufficient (references/encryption.md:27-30) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | Configure your Azure Key Vault instance: "Your Azure Key Vault instance must be accessible through public network access or allow trusted Microsoft services to bypass its firewall. An instance that is exclusively accessible through private endpoints can't be us | 2026-11-09 | UNVERIFIED |
|
|
119
|
+
| CP-E313 | Continuous backup with CMK requires system- or user-assigned managed identity; first-party identity not supported (references/encryption.md:32-33) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | FAQ: How do customer-managed keys affect continuous backups?: "you must use a system-assigned or user-assigned managed identity in the Key Vault access policy. Azure Cosmos DB first-party identities aren't currently supported on accounts using continuous backups." | 2026-11-09 | VERIFIED |
|
|
120
|
+
| CP-E314 | Periodic-backup restore needs original key version; temporary first-party identity access if source used system-assigned identity (references/encryption.md:34-36) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | FAQ: How do customer-managed keys affect periodic backups?: "The encryption key that you used at the time of the backup is required and must be available in Azure Key Vault." and "If you used a system-assigned managed identity in the access policy, temporarily grant access to the | 2026-11-09 | VERIFIED |
|
|
121
|
+
| CP-E315 | Restored CMK account: identity metadata can stay bound to the source; assign a new identity to the restored account (references/encryption.md:39-43) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | Assign a new managed-identity to the restored database account: "The identity metadata is bound with the source database account and restore workflow doesn't rescope identity to the target database account." | 2026-11-09 | VERIFIED |
|
|
122
|
+
| CP-E316 | Revocation/disabled keys can block data and recovery (references/encryption.md:44) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | FAQ: What operations are available after a customer-managed key is revoked?: "Account deletion is the only operation possible when the encryption key has been revoked." | 2026-11-09 | VERIFIED |
|
|
123
|
+
| CP-E317 | Names, indexed paths and partition-key values are not all hidden by CMK (references/encryption.md:47-48) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | FAQ: What data gets encrypted with the customer-managed keys?: "All the data ... is encrypted with the customer-managed keys, except for the following metadata: The names of your ... accounts, databases, and containers ... The property paths declared in your indexing policies ... Th | 2026-11-09 | UNVERIFIED |
|
|
124
|
+
| CP-E318 | Namespace Microsoft.DocumentDB/databaseAccounts; metrics TotalRequests (StatusCode/OperationType/DatabaseName/CollectionName/Region), TotalRequestUnits, NormalizedRUConsumption Max by PartitionKeyRangeId/PhysicalPartitionId (references/monitoring.md:3,10) | https://learn.microsoft.com/azure/cosmos-db/monitor-reference | Supported metrics for Microsoft.DocumentDB/DatabaseAccounts: "`NormalizedRUConsumption` / No / Percent / Maximum, Average / `CollectionName`, `DatabaseName`, `Region`, `PartitionKeyRangeId`, `CollectionRid`, `PhysicalPartitionId`, `OfferOwnerRid`"; `TotalRequests` dims include `St | 2026-11-09 | VERIFIED |
|
|
125
|
+
| CP-E319 | ServerSideLatencyDirect / ServerSideLatencyGateway exist; old ServerSideLatency deprecated (references/monitoring.md:11) | https://learn.microsoft.com/azure/cosmos-db/monitor-reference | Supported metrics for Microsoft.DocumentDB/DatabaseAccounts: "(deprecated) Server Side Latency ... will be removed from Azure Monitor at the end of August 2025. Please use \"Server Side Latency Direct\" and \"Server Side Latency Gateway\"" | 2026-11-09 | VERIFIED |
|
|
126
|
+
| CP-E320 | ARM API version 2025-04-15 exists for databaseAccounts, sqlDatabases, containers (references/provisioning.md:7; assets/account.arm.json:11,29,36) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/templates/microsoft.documentdb/2025-04-15/databaseaccounts | Page title: "Microsoft.DocumentDB databaseAccounts/sqlDatabases/containers 2025-04-15" (container page; account page of same version fetched and served) | 2026-11-09 | UNVERIFIED |
|
|
127
|
+
| CP-E321 | ARM account properties: kind GlobalDocumentDB, databaseAccountOfferType Standard, locations[locationName,failoverPriority,isZoneRedundant], consistencyPolicy.defaultConsistencyLevel Session, enableAutomaticFailover, enableMultipleWriteLocations, disableLocalAuth, minimalTlsVersion Tls12, publicNetworkAccess Disabled (assets/account.arm.json:14-23; references/provisioning.md:11,15-16) | https://learn.microsoft.com/azure/templates/microsoft.documentdb/2025-04-15/databaseaccounts | Property values (account): "minimalTlsVersion / ... / 'Tls''Tls11''Tls12'"; "publicNetworkAccess / ... / 'Disabled''Enabled''SecuredByPerimeter'"; "disableLocalAuth / Opt-out of local authentication and ensure only MSI and AAD can be used… | 2026-11-09 | VERIFIED |
|
|
128
|
+
| CP-E322 | backupPolicy.continuousModeProperties.tier Continuous7Days; pinned 2025-04-15 ARM schema does not expose a 35-day tier (assets/account.arm.json:24; references/provisioning.md:18; references/commands/backup/continuous.md:5-6) | https://learn.microsoft.com/azure/templates/microsoft.documentdb/2025-04-15/databaseaccounts | ContinuousModeProperties: "tier / Enum to indicate type of Continuous backup mode / 'Continuous30Days''Continuous7Days'" (no Continuous35Days value in this API version) | 2026-11-09 | VERIFIED |
|
|
129
|
+
| CP-E323 | Container: partitionKey paths/kind Hash/version 2, defaultTtl -1, indexingPolicy (consistent, automatic, includedPaths, excludedPaths, compositeIndexes order ascending/descending), options.throughput 400 (assets/account.arm.json:42-52; references/provisioning.md:12-14) | https://learn.microsoft.com/azure/templates/microsoft.documentdb/2025-04-15/databaseaccounts/sqldatabases/containers | Property values: "version / Indicates the version of the partition key definition / int Constraints:Min value = 1Max value = 2"; "order / Sort order for composite paths. / 'ascending''descending'"; "throughput / Request Units per second. | 2026-11-09 | VERIFIED |
|
|
130
|
+
| CP-E324 | Account name 3-44 chars, lowercase letters/numbers/hyphens (assets/account.arm.json:5 (maxLength 44); assets/provision.sh:10) | https://learn.microsoft.com/azure/azure-resource-manager/management/resource-name-rules | Microsoft.DocumentDB: "databaseAccounts / global / 3-44 / Lowercase letters, numbers, and hyphensStart with lowercase letter or number." BUT ARM schema page (2025-04-15 databaseaccounts) says: "name / The resource name / string Constraints:Mi | 2026-11-09 | CONFLICT |
|
|
131
|
+
| CP-E325 | `az cosmosdb sql container create` flags `--partition-key-path`, `--partition-key-version`, `--throughput`, `--ttl -1`, `--idx @file`, `--vector-embeddings @file` (references/provisioning.md:48-49; assets/provision.sh:28-31) | https://learn.microsoft.com/cli/azure/cosmosdb/sql/container | az cosmosdb sql container create: "--ttl Default TTL. If the value is missing or set to \"-1\", items don't expire." Syntax block lists `[--idx] ... [--partition-key-version] [--throughput] [--ttl] ... [--vector-embeddings]` | 2026-11-09 | VERIFIED |
|
|
132
|
+
| CP-E326 | `az cosmosdb create` flags `--kind GlobalDocumentDB`, `--locations`, `--default-consistency-level`, `--backup-policy-type`, `--continuous-tier`, `--enable-automatic-failover`, `--enable-multiple-write-locations`, `--disable-local-auth`, `--public-network-access DISABLED`, `--minimal-tls-version Tls12` (assets/provision.sh:21-25) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/cli/azure/cosmosdb | az cosmosdb create: Syntax block: `[--backup-policy-type {Continuous, Periodic}] ... [--continuous-tier {Continuous30Days, Continuous7Days}] ... [--disable-local-auth {false, true}] ... [--kind {GlobalDocumentDB, MongoDB, Parse}] ... [--min | 2026-11-09 | UNVERIFIED |
|
|
133
|
+
| CP-E327 | Vector search needs account capability `EnableNoSQLVectorSearch` (references/provisioning.md:46) | https://learn.microsoft.com/azure/cosmos-db/vector-search | Enable the vector indexing and search feature: "az cosmosdb update --resource-group <resource-group-name> --name <account-name> --capabilities EnableNoSQLVectorSearch" | 2026-11-09 | VERIFIED |
|
|
134
|
+
| CP-E328 | Vector policies float32/1536 with diskANN; "don't assume float16 works in this pinned schema" (references/provisioning.md:50-51). Note: float32/1536/diskANN); float16 caveat UNVERIFIED for 2025-04-15 | https://learn.microsoft.com/azure/cosmos-db/vector-search | Container vector policies; Vector indexing policies: "Supported types are `float32`, `float16`, `int8`, and `uint8`." and diskANN max dimensions "4096". float32/1536/diskANN are valid; the docs do list float16 as supported, so the skill's float16 caution is a hedge about t | 2026-11-09 | VERIFIED |
|
|
135
|
+
| CP-E329 | Continuous has 7/30/35-day tiers; CLI/ARM exposure of the newest tier varies (references/recovery.md:5-7; references/commands/backup/continuous.md:5-6) | https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore | Backup modes: "Continuous backup mode: This mode has three tiers: 7-day, 30-day, and 35-day retention." Core CLI `--continuous-tier {Continuous30Days, Continuous7Days}` (az cosmosdb create/update), preview extension lists `Continuous3 | 2026-11-09 | VERIFIED |
|
|
136
|
+
| CP-E330 | Continuous cannot be switched back to periodic (references/recovery.md:5-6; references/commands/backup/continuous.md:12-13) | https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore | Backup modes (note): "If your account is configured in continuous mode, you can't switch it back to periodic mode." | 2026-11-09 | VERIFIED |
|
|
137
|
+
| CP-E331 | Continuous capture in steady state within about 100 seconds; multi-write: only hub-confirmed mutations restorable (references/recovery.md:25-26; references/replication.md:13-14) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction | What is restored into a new account?; Understand multi-region write account restore: "In a steady state, all mutations performed on the source account ... are backed up asynchronously within 100 seconds." / "the restore process only restores the documents confirmed by the hub region by the restore point | 2026-11-09 | VERIFIED |
|
|
138
|
+
| CP-E332 | Strong consistency and multi-region writes not simultaneously supported (references/replication.md:6-7) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/multi-region-writes | Best practices for multi-region writes: "You can't configure multi-region write accounts for strong consistency." (also consistency-levels page: "Azure Cosmos DB accounts with multiple write regions can't use strong consistency") | 2026-11-09 | UNVERIFIED |
|
|
139
|
+
| CP-E333 | Continuous backups are taken in account regions; restored new accounts don't recreate all original regions/network/roles; recovery point needs resource/region to have existed (references/replication.md:10-14) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction | Continuous backup intro; What isn't restored?: "Continuous backups are taken in every region where the account exists." / "The following configurations aren't restored ...: Firewall, virtual network, data plane role-based access control, or private endpoint settings. | 2026-11-09 | VERIFIED |
|
|
140
|
+
| CP-E334 | `az cosmosdb show`, `az cosmosdb sql container show`, `az cosmosdb sql container throughput show` exist (references/commands/azure-cli.md:10-17; references/commands/audit/live.md:8-9) | https://learn.microsoft.com/cli/azure/cosmosdb/sql/container | Commands table: "az cosmosdb sql container show / Show the details of a SQL container ..." and "az cosmosdb sql container throughput show / Get the throughput of the SQL container ..." | 2026-11-09 | VERIFIED |
|
|
141
|
+
| CP-E335 | `az cosmosdb update --backup-interval --backup-retention` (minutes/hours); periodic interval 60-1440 min, retention >= 2x interval and <= 720 h (references/commands/azure-cli.md:27-30; references/commands/backup/periodic.md:8-9) | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-modify-interval-retention | Modify backup options for an existing account: "Backup Interval can't be less than 1 hour and greater than 24 hours." / "The minimum retention period can't be less than two times the backup interval (in hours) and it can't be greater than 720 hours." CLI doc: `--back | 2026-11-09 | VERIFIED |
|
|
142
|
+
| CP-E336 | Periodic default: backup every 4 hours, latest two copies retained (references/commands/backup/periodic.md:4-6) | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction | How Azure Cosmos DB performs data backup: "Azure Cosmos DB automatically takes a full backup of your database every 4 hours. At any point of time, only the latest two backups are stored by default." | 2026-11-09 | VERIFIED |
|
|
143
|
+
| CP-E337 | Actual completion can lag the configured interval (references/commands/backup/periodic.md:5-6) | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-modify-interval-retention | Modify backup options (Backup Interval): "it doesn't guarantee that the backup completes within that time interval." | 2026-11-09 | VERIFIED |
|
|
144
|
+
| CP-E338 | Redundancy Geo/Local/Zone; changing it affects future backups, can take twice the interval, immediately loses access to older backups (references/commands/backup/periodic.md:9-13) | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-modify-interval-retention | Backup storage redundancy bullet: "it may take up to twice the backup interval time for the changes to take effect, and **you will lose access to restore the older backups immediately.**" CLI: `--backup-redundancy {Geo, Local, Zone}` | 2026-11-09 | VERIFIED |
|
|
145
|
+
| CP-E339 | Escalate promptly; raise retention to at least seven days, within eight hours (references/commands/backup/periodic.md:17-18; references/commands/restore/periodic-support.md:14-15) | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-request-data-restore | Request data restoration: "make sure to increase the backup retention for your account to at least seven days. It's best to increase your retention within 8 hours of this event." | 2026-11-09 | VERIFIED |
|
|
146
|
+
| CP-E340 | Deleted container/database snapshots retained 30 days; shared-throughput backup/restore is database-scope (references/commands/backup/periodic.md:21-25) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction | How Azure Cosmos DB performs data backup: "If the container or database is deleted, Azure Cosmos DB retains the existing snapshots of a given provisioned throughput container or shared throughput database for 30 days. If throughput is provisioned at the database | 2026-11-09 | UNVERIFIED |
|
|
147
|
+
| CP-E341 | Periodic restore is via Azure Support, always into a new account, no precreated target; support plan needed (references/commands/backup/periodic.md:3; references/commands/restore/periodic-support.md:3-12) | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-request-data-restore | Request data restoration; Considerations: "A new Azure Cosmos DB account is created to hold the restored data when restoring from a backup ... You can't restore data to a precreated Azure Cosmos DB account." / "Azure support isn't available with **Basic** plan." | 2026-11-09 | VERIFIED |
|
|
148
|
+
| CP-E342 | Latest restorable timestamp is per resource/region; aggregate = minimum across containers (references/commands/backup/continuous.md:7-8; references/commands/recovery-target.md:5-6) | https://learn.microsoft.com/azure/cosmos-db/get-latest-restore-timestamp | SQL account (script): "Latest restorable timestamp for an account is minimum of restorable timestamps of all the underlying containers" | 2026-11-09 | VERIFIED |
|
|
149
|
+
| CP-E343 | Tier change/migration shortens usable history; shorter tier loses older recovery points; new tier does not create older backups (references/commands/backup/continuous.md:9-10,13) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/migrate-continuous-backup | Change Continuous Mode tiers: "When you switch to a shorter retention window ..., you immediately lose the ability to restore data older than the new window. When you switch to a longer retention window ..., you can only restore data from the… | 2026-11-09 | UNVERIFIED |
|
|
150
|
+
| CP-E344 | Continuous backup redundancy is platform-controlled (local; zone-redundant where zones enabled), no switch (references/commands/backup/continuous.md:13-15) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction | Backup storage redundancy: "In continuous backup mode, you can't update the backup storage redundancy." and "By default, each region stores the backup in locally redundant storage accounts. If the region has availability zones enabled, then the ba | 2026-11-09 | VERIFIED |
|
|
151
|
+
| CP-E345 | `az cosmosdb sql retrieve-latest-backup-time` with `--account-name --database-name --container-name --location` (extension caveat) (references/commands/backup/continuous.md:11-12,20-26) | https://learn.microsoft.com/azure/cosmos-db/get-latest-restore-timestamp | SQL container / CLI: "az cosmosdb sql retrieve-latest-backup-time -g {resourcegroup} -a {accountname} -d {db_name} -c {container_name} -l {location}" (CLI ref lists it as a required `--container-name -c`, `--location -l`; no extension… | 2026-11-09 | VERIFIED |
|
|
152
|
+
| CP-E346 | Azure CLI 2.58.0+ required for in-account restore command (references/commands/restore/continuous-deleted-resource.md:9) | https://learn.microsoft.com/azure/cosmos-db/how-to-restore-in-account-continuous-backup | Restore a deleted container or database (Azure CLI tab): "The Azure CLI version 2.58.0 or later is required to access the in-account restore command." | 2026-11-09 | VERIFIED |
|
|
153
|
+
| CP-E347 | `az cosmosdb sql container restore --resource-group --account-name --database-name --name --restore-timestamp --disable-ttl True` restores a deleted container in the same account (references/commands/restore/continuous-deleted-resource.md:22-25 (and 15-17)) | https://learn.microsoft.com/azure/cosmos-db/how-to-restore-in-account-continuous-backup | Restore a deleted container or database (Azure CLI, NoSQL pivot): "Initiate a restore operation for a deleted container by using `az cosmosdb sql container restore` ... `--database-name <database-name> --name <container-name> --restore-timestamp <timestamp> --disable-ttl True`". CLI re | 2026-11-09 | VERIFIED |
|
|
154
|
+
| CP-E348 | `az cosmosdb sql database restore` restores a deleted database (and child containers) in the same account (references/commands/restore/continuous-deleted-resource.md:15-17) | https://learn.microsoft.com/azure/cosmos-db/how-to-restore-in-account-continuous-backup | Restore a deleted container or database (Azure CLI tab): "Use the Azure CLI to restore a deleted container or database. Child containers are also restored." and "Initiate a restore operation for a deleted database by using `az cosmosdb sql database restore`." | 2026-11-09 | VERIFIED |
|
|
155
|
+
| CP-E349 | Service may default an omitted timestamp to latest deleted instance (references/commands/restore/continuous-deleted-resource.md:28-30) | https://learn.microsoft.com/azure/cosmos-db/how-to-restore-in-account-continuous-backup | Restore a deleted container or database (CLI steps 4-5): "The restore timestamp is optional, if it isn't provided last deleted instance of container is restored." | 2026-11-09 | VERIFIED |
|
|
156
|
+
| CP-E350 | In-account restore only for deleted resources, never live/existing ones; restore time before deletion within window (references/commands/restore/continuous-deleted-resource.md:4-7; references/commands/restore.md:8; references/recovery.md:18-20) | https://learn.microsoft.com/azure/cosmos-db/restore-in-account-continuous-backup-introduction | In-account restore scenarios: "The in-account restore feature doesn't allow restoring existing (or not-deleted) databases or containers within the same account. To restore live resources, target the restore operation to a new account." | 2026-11-09 | VERIFIED |
|
|
157
|
+
| CP-E351 | Restored resources are new: session/continuation tokens invalid; restart SDK clients and queries (references/commands/restore/continuous-deleted-resource.md:37-40) | https://learn.microsoft.com/azure/cosmos-db/restore-in-account-continuous-backup-introduction | What is restored? (Note): "those resource should be treated as new resources. Existing session or continuation tokens in use from your client applications become invalid." | 2026-11-09 | VERIFIED |
|
|
158
|
+
| CP-E352 | Change feed restarts from beginning; only post-restore lifetime events; pre-deletion events not propagated (references/commands/restore/continuous-deleted-resource.md:42-45) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/azure/cosmos-db/restore-in-account-continuous-backup-introduction | What is restored? (Note): "it should restart the change feed from the beginning after a restore operation. The restored resource will have only the change feed events starting from the lifetime of the resource after restore. All change feed event | 2026-11-09 | UNVERIFIED |
|
|
159
|
+
| CP-E353 | In-account restore shows as InAccount restore activity (references/commands/restore/continuous-deleted-resource.md:31) | https://learn.microsoft.com/azure/cosmos-db/how-to-restore-in-account-continuous-backup | Track the status of a restore operation: "the operation is identified as an **InAccount** restore operation on the resource." | 2026-11-09 | VERIFIED |
|
|
160
|
+
| CP-E354 | No more than three restore operations can be active at any time on the same account (commands/restore/continuous-deleted-resource.md) | https://learn.microsoft.com/azure/cosmos-db/how-to-restore-in-account-continuous-backup | Restore a deleted container or database: "No more than three restore operations can be active at any time on the same account." | 2026-11-09 | VERIFIED |
|
|
161
|
+
| CP-E355 | `az cosmosdb restore` flags: `--account-name` (source), `--target-database-account-name`, `--location`, `--restore-timestamp`, `--resource-group`, `--disable-ttl`, `--disable-local-auth`, `--public-network-access DISABLED` (references/commands/restore/continuous-new-account.md:12-16) Note: the orchestrator's 2026-11-09 mechanical re-check could not confirm this quote on the fetched page (dynamic content, code block or bot protection); treat as unconfirmed. | https://learn.microsoft.com/cli/azure/cosmosdb | az cosmosdb restore: Syntax: `az cosmosdb restore --account-name --location --resource-group --restore-timestamp --target-database-account-name [--disable-local-auth {false, true}] [--disable-ttl {false, true}] ... [--public-network-access { | 2026-11-09 | UNVERIFIED |
|
|
162
|
+
| CP-E356 | Partial restore via repeated `--databases-to-restore name=DatabaseName collections=c1 c2` (references/commands/restore/continuous-new-account.md:23-25) | https://learn.microsoft.com/cli/azure/cosmosdb | az cosmosdb restore (--databases-to-restore): "Usage: --databases-to-restore name=DatabaseName collections=collection1 [collection2 ...] Multiple databases can be specified by using more than one `--databases-to-restore` argument." | 2026-11-09 | VERIFIED |
|
|
163
|
+
| CP-E357 | ARM restore uses `createMode: Restore` / `restoreParameters.restoreSource` (full restorable-resource ID) (references/commands/restore/continuous-new-account.md:19-22) | https://learn.microsoft.com/azure/cosmos-db/restore-account-continuous-backup | Restore using the Azure Resource Manager template: `"createMode": "Restore", "restoreParameters": {"restoreSource": "/subscriptions/.../providers/Microsoft.DocumentDB/locations/West US/restorableDatabaseAccounts/...", "restoreMode": "PointInTime", "restoreTimestampInUtc" | 2026-11-09 | VERIFIED |
|
|
164
|
+
| CP-E358 | Restore is same-subscription only; precreated account not the destination (references/commands/restore/continuous-new-account.md:5-7; references/commands/recovery-target.md:9-10) | https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore | Frequently asked questions: "Can I restore from an account A in subscription S1 to account B in a subscription S2? No. You can only restore between accounts within the same subscription." | 2026-11-09 | VERIFIED |
|
|
165
|
+
| CP-E359 | A subset of containers in a shared-throughput database cannot be restored; restore the whole database (references/commands/restore/continuous-new-account.md:26-27) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction | What isn't restored?: "A subset of containers under a shared throughput database can't be restored. The entire database can be restored as a whole." | 2026-11-09 | VERIFIED |
|
|
166
|
+
| CP-E360 | Data/index/consistency restored, throughput may not match; firewall/VNet/private endpoints, data RBAC, regions, stored procs/triggers/UDFs, RBAC assignments not restored (references/commands/restore/continuous-new-account.md:36-41; references/recovery.md (new-account)) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction | What isn't restored?; Current limitations: "Continuous mode restore might not restore throughput setting valid as of restore point." / "Stored procedures, triggers, UDFs." / "Role-based access control assignments." | 2026-11-09 | VERIFIED |
|
|
167
|
+
| CP-E361 | TTL: default restore restores TTL config and can delete data; disable TTL on restore (references/commands/restore/continuous-new-account.md:43-44; references/commands/recovery-target.md:21-22) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction | Time to live: "The default restore process restores all the properties of a container including its TTL configuration by default. This can result in deletion of data if restore is done without disabling the TTL." | 2026-11-09 | VERIFIED |
|
|
168
|
+
| CP-E362 | CMK restore needs `--assign-identity` / `--default-identity` (references/commands/restore/continuous-new-account.md:27-28) | https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk | Restore a continuous account that is configured with managed identity: "A user-assigned identity is required in the restore request because the source account managed identity ... can't be carried over automatically to the target database account." Command uses `--assign-identity $identityI | 2026-11-09 | VERIFIED |
|
|
169
|
+
| CP-E363 | Index may be rebuilding after restore (IndexTransformationProgress) (references/commands/restore/continuous-new-account.md:35-37; references/commands/recovery-target.md:25-27) | https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction | Current limitations: "After restoring, it's possible that for certain collections the consistent index might be rebuilding." | 2026-11-09 | VERIFIED |
|
|
170
|
+
| CP-E364 | `az cosmosdb restore` is not for periodic accounts (periodic restore goes through support) (references/commands/restore/periodic-support.md:3-4) | https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore | Backup modes: "Periodic backup mode: ... the data is restored by creating a request with the support team." / "If you configure a new account with continuous backup, you can do self-service restore via Azure portal, PowerShell, or CLI | 2026-11-09 | VERIFIED |
|
|
171
|
+
| CP-E365 | Periodic restore always creates a new account; settings not carried over (VNET ACLs, stored procs/triggers/UDFs, multi-region, managed identity) (references/commands/restore/periodic-support.md:16-17; references/commands/backup/periodic.md:24) | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-request-data-restore | Considerations for restoring the data from a backup (Note): "The following settings are not carried over to the new account: VNET access control lists; Stored procedures, triggers and user-defined functions; Multi-region settings; Managed identity settings" | 2026-11-09 | VERIFIED |
|
|
172
|
+
| CP-E366 | No user-named/on-demand backup objects; platform-managed only (references/commands/backup.md:5-7; references/recovery.md:3-5) | https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore | Immutability of Cosmos DB backups: "Cosmos DB backups aren't exposed to any human actors, customers, or any other module for listing, deletion, or disabling of backups." | 2026-11-09 | VERIFIED |
|
|
173
|
+
| CP-E367 | Soft-delete (preview) is a separate lifecycle feature, not assumed enabled, not a backup replacement (references/recovery.md:20-21) | https://learn.microsoft.com/azure/cosmos-db/soft-delete | Soft delete for Azure Cosmos DB (preview) - FAQ: "Soft delete is enabled at the Azure Cosmos DB account level." and "In preview, the Azure Cosmos DB product team manages enablement." Also: soft delete "Complements backup and DR strategies" | 2026-11-09 | VERIFIED |
|
|
174
|
+
| CP-E368 | Source names can be reused so restorable instance ID is needed (references/commands/recovery-target.md:3-4) | https://learn.microsoft.com/azure/cosmos-db/periodic-backup-request-data-restore | Request data restoration: "If you create another account with the same name as the deleted account, share that with the support team because it helps to determine the right account to choose." (Instance-ID usage: restore-account-continuous-backup | 2026-11-09 | VERIFIED |
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
# Indexing / RU capacity
|
|
2
|
+
|
|
3
|
+
NoSQL containers default to consistent indexing of JSON properties. This isn't a
|
|
4
|
+
GSI/LSI system: no per-index provisioned throughput, projection table or separate
|
|
5
|
+
index query resource. Index policy affects write RUs, storage and query execution.
|
|
6
|
+
|
|
7
|
+
| Need | Native mechanism | Validation |
|
|
8
|
+
|---|---|---|
|
|
9
|
+
| Equality/range/order by one scalar | Range index on path | Query metrics, indexed paths and type/order |
|
|
10
|
+
| ORDER BY multiple properties | Matching composite index | Match path sequence and ASC/DESC directions; reverse all directions may work, not arbitrary mix |
|
|
11
|
+
| Geospatial | Spatial index/type | GeoJSON semantics and regional/query cost |
|
|
12
|
+
| Native vectors | Vector embedding policy AND vector index | Same concrete path; selected type/dimensions constraints |
|
|
13
|
+
| Exclude large unused properties | includedPaths/excludedPaths | More-specific path precedence; don't accidentally exclude queried fields |
|
|
14
|
+
|
|
15
|
+
Use parameterized SQL, selective projections and routed partition keys. Queries
|
|
16
|
+
can scan even when syntax is valid; don't call a cross-partition query a point read.
|
|
17
|
+
Index transformations are asynchronous: confirm progress and query behavior before
|
|
18
|
+
cutover; adding index policy isn't measured optimization by itself.
|
|
19
|
+
|
|
20
|
+
RU is normalized operation work, not requests per second. Item size/indexes/query
|
|
21
|
+
shape/consistency/regions all matter. Dedicated manual throughput example uses
|
|
22
|
+
400 RU/s; autoscale has a configured maximum and dynamic minimum; serverless bills
|
|
23
|
+
consumption and has different limits. Database shared throughput and per-container
|
|
24
|
+
throughput are distinct, not additive synonyms. Never set manual and autoscale
|
|
25
|
+
max simultaneously or apply provisioned-throughput commands to serverless.
|
|
26
|
+
|
|
27
|
+
Choose minimum/capacity from current service rules and observed workload, not a
|
|
28
|
+
blanket “400 fits production.” Autoscale doesn't fix a hot key. Inspect normalized
|
|
29
|
+
RU by partition, 429 rates, Retry-After, per-operation charges, request/diagnostic
|
|
30
|
+
latency and index utilization; capture consistency/session and connection mode.
|
|
31
|
+
Global replication creates regional charges; backup/vector/index/CMK choices may
|
|
32
|
+
add costs. Refresh price/region assumptions before any budget claim.
|
|
33
|
+
|
|
34
|
+
Sources: [index policy](https://learn.microsoft.com/azure/cosmos-db/index-policy),
|
|
35
|
+
[manage indexes](https://learn.microsoft.com/azure/cosmos-db/how-to-manage-indexing-policy),
|
|
36
|
+
[request units](https://learn.microsoft.com/azure/cosmos-db/request-units),
|
|
37
|
+
[throughput](https://learn.microsoft.com/azure/cosmos-db/set-throughput).
|
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
# Language adapters — load the matching section only
|
|
2
|
+
|
|
3
|
+
Keep the existing SDK/version and credential flow. No install is required by the
|
|
4
|
+
skill; SDK snippets below are illustrative and **not compiled against installed
|
|
5
|
+
SDKs**. The injected JS example is tested with fakes, not Azure. Do not claim every
|
|
6
|
+
SDK supports every vector/change-feed/Entra/continuation feature identically.
|
|
7
|
+
|
|
8
|
+
| Language | First-party path checked 2026-11-08 | Adapter obligations |
|
|
9
|
+
|---|---|---|
|
|
10
|
+
| JavaScript / TypeScript | `@azure/cosmos`, `@azure/identity` | Singleton CosmosClient, server credential, partitionKey, parameterized query, fetchNext token/session/charge, ETag |
|
|
11
|
+
| Java | `com.azure:azure-cosmos` v4 | CosmosAsyncClient/Container, PartitionKey, CosmosQueryRequestOptions, paged Flux/continuation and diagnostics |
|
|
12
|
+
| Kotlin/JVM | Existing Java v4 SDK via JVM interop | No separate Kotlin-native NoSQL SDK claim; adapt Reactor/coroutines/cancellation deliberately |
|
|
13
|
+
| Rust | Microsoft `azure_data_cosmos` + `azure_identity`, **public preview** | Current official quickstart warns no SLA/not recommended for production; verify pinned API/feature support, don't import community SDK as first-party GA |
|
|
14
|
+
| PHP | No first-party NoSQL PHP SDK identified in retrieved official SDK matrix | NoSQL HTTPS REST adapter or explicitly reviewed community package; no fake official PHP class names |
|
|
15
|
+
| Python | `azure-cosmos`, `azure-identity` | `query_items` with `partition_key` [CP-E174], response hooks/ETags; newer streamable cross-partition continuation supported, aggregate cross-partition restrictions remain; verify pinned version |
|
|
16
|
+
| .NET | `Microsoft.Azure.Cosmos` v3 | CosmosClient/Container, FeedIterator, PartitionKey, IfMatchEtag/session token, TransactionalBatch |
|
|
17
|
+
| Go | `github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos` | Explicit partition keys, pager/cancellation/charges and SDK-specific retry behavior |
|
|
18
|
+
| Other | Existing supported SDK or NoSQL REST | Port the same correctness contract; no universal feature/compilation claim |
|
|
19
|
+
|
|
20
|
+
## JS / TS
|
|
21
|
+
|
|
22
|
+
Use [runtime.mjs](../assets/runtime.mjs) with an already-authorized injected
|
|
23
|
+
`Container`; it doesn't construct a client or call on import. Actual app setup
|
|
24
|
+
uses `new CosmosClient({endpoint, aadCredentials: credential})` with an existing
|
|
25
|
+
approved Entra credential, database/container selected explicitly. No keys/logging.
|
|
26
|
+
|
|
27
|
+
```javascript
|
|
28
|
+
// Illustrative actual SDK transactional batch; same tenant/full partition only.
|
|
29
|
+
const result = await container.items.batch([
|
|
30
|
+
{operationType: "Create", resourceBody: order},
|
|
31
|
+
{operationType: "Create", resourceBody: outbox}
|
|
32
|
+
], authenticatedTenant);
|
|
33
|
+
// Verify batch result and individual errors; bulk != transactional batch.
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
## Java
|
|
37
|
+
|
|
38
|
+
```java
|
|
39
|
+
CosmosQueryRequestOptions options = new CosmosQueryRequestOptions()
|
|
40
|
+
.setPartitionKey(new PartitionKey(authenticatedTenant));
|
|
41
|
+
SqlQuerySpec query = new SqlQuerySpec(
|
|
42
|
+
"SELECT * FROM c WHERE c.tenantId=@tenant",
|
|
43
|
+
List.of(new SqlParameter("@tenant", authenticatedTenant)));
|
|
44
|
+
container.queryItems(query, options, Order.class)
|
|
45
|
+
.byPage(continuationToken, 50); // subscribe/consume with bounds/cancellation
|
|
46
|
+
// replaceItem(..., new CosmosItemRequestOptions().setIfMatchETag(etag)) for OCC.
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
## Kotlin/JVM
|
|
50
|
+
|
|
51
|
+
```kotlin
|
|
52
|
+
val options = CosmosQueryRequestOptions().setPartitionKey(PartitionKey(tenant))
|
|
53
|
+
val query = SqlQuerySpec("SELECT * FROM c WHERE c.tenantId=@tenant",
|
|
54
|
+
listOf(SqlParameter("@tenant", tenant)))
|
|
55
|
+
val pages = container.queryItems(query, options, Order::class.java).byPage(cursor, 50)
|
|
56
|
+
// Explicit bounded Reactor/coroutine consumption; don't block an event loop.
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
## Rust — official preview, not GA
|
|
60
|
+
|
|
61
|
+
```rust
|
|
62
|
+
// ContainerClient injected; snippet follows official quickstart's preview API.
|
|
63
|
+
let response = container.read_item(tenant, order_id, None).await?;
|
|
64
|
+
// query_items::<Order>(Query::from(...).with_parameter(...)? , tenant, None)?
|
|
65
|
+
// Consume pager with cancellation/charge/continuation policy for pinned crate.
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
## PHP / other REST
|
|
69
|
+
|
|
70
|
+
Use approved Entra token provider; Cosmos data-plane REST authorization value is
|
|
71
|
+
URL-encoded `type=aad&ver=1.0&sig=<token>`. Never dump tokens or implement homemade
|
|
72
|
+
credential acquisition. Token scope/audience/cloud endpoint must match service.
|
|
73
|
+
HTTPS POST `/dbs/ordersdb/colls/orders/docs` with these request values:
|
|
74
|
+
|
|
75
|
+
```php
|
|
76
|
+
$body = json_encode([
|
|
77
|
+
'query' => 'SELECT * FROM c WHERE c.tenantId=@tenant',
|
|
78
|
+
'parameters' => [['name' => '@tenant', 'value' => $authenticatedTenant]]
|
|
79
|
+
], JSON_THROW_ON_ERROR);
|
|
80
|
+
$headers = [
|
|
81
|
+
'Authorization: ' . $alreadyEncodedCosmosEntraAuthorization,
|
|
82
|
+
'x-ms-version: 2018-12-31',
|
|
83
|
+
'x-ms-date: ' . gmdate('D, d M Y H:i:s') . ' GMT',
|
|
84
|
+
'x-ms-documentdb-isquery: True',
|
|
85
|
+
'x-ms-documentdb-partitionkey: ' . json_encode([$authenticatedTenant], JSON_THROW_ON_ERROR),
|
|
86
|
+
'x-ms-max-item-count: 50',
|
|
87
|
+
'Content-Type: application/query+json'
|
|
88
|
+
];
|
|
89
|
+
// Inject existing HTTP client; add opaque x-ms-continuation/session-token when
|
|
90
|
+
// resuming, then capture response continuation/session/charge/activity-id/status.
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
Do not let client input choose tenant/endpoint/container. Parameterize all values;
|
|
94
|
+
URL-encode resource IDs safely, preserve partition JSON types and use If-Match for
|
|
95
|
+
conditional writes. Bound time/retries/pages/RUs; an empty page can continue. A
|
|
96
|
+
REST example isn't permission to send requests or a tested PHP SDK integration.
|
|
97
|
+
|
|
98
|
+
## Portable adapter contract
|
|
99
|
+
|
|
100
|
+
`read(id, typedPartition, session, deadline)`; `query(query+parameters, partition,
|
|
101
|
+
opaqueCursor, pageSize, session, budget)` → items + continuation + session + RU +
|
|
102
|
+
activityID; `replace(id, partition, body, expectedEtag, deadline)`; `batch(fullKey,
|
|
103
|
+
operations)`. Preserve 404/409/412/429/unknown-write distinctions, tenant binding,
|
|
104
|
+
finite numeric/vector/schema values, safe cancellation and replay/idempotency.
|
|
105
|
+
No missing RU as zero, partial-page cursor skipping or arbitrary retry of writes.
|
|
106
|
+
|
|
107
|
+
Sources: [SDKs](https://learn.microsoft.com/azure/cosmos-db/nosql/sdk-nodejs),
|
|
108
|
+
[Rust preview](https://learn.microsoft.com/azure/cosmos-db/quickstart-rust),
|
|
109
|
+
[Go](https://learn.microsoft.com/azure/cosmos-db/quickstart-go),
|
|
110
|
+
[Java query API](https://learn.microsoft.com/java/api/com.azure.cosmos.cosmosasynccontainer),
|
|
111
|
+
[REST query](https://learn.microsoft.com/rest/api/cosmos-db/query-documents),
|
|
112
|
+
[REST authorization](https://learn.microsoft.com/rest/api/cosmos-db/access-control-on-cosmosdb-resources).
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# June / December review — in-session reminder only
|
|
2
|
+
|
|
3
|
+
Run `python3 scripts/review_due.py --as-of YYYY-MM-DD` with the actual client-local
|
|
4
|
+
date at substantive use, not help. It reads assets/content-review.json and prints
|
|
5
|
+
due status; never writes, schedules, advances dates or contacts any provider.
|
|
6
|
+
Initial next full review is **2026-12-01**. After that date it remains overdue even
|
|
7
|
+
if June/December windows pass. Invalid/missing dates fail, not default to server UTC.
|
|
8
|
+
|
|
9
|
+
Full review checklist: scope/API/SDK support, runtime/partition/transaction limits,
|
|
10
|
+
index/vector constraints/lifecycle, data/control roles/CMK identities and recovery,
|
|
11
|
+
backup tiers/modes/windows/CLI/ARM schema, metric deprecations, all selected routes,
|
|
12
|
+
provisioning equivalence, negative/fakeCLI/runtime tests and adversarial prompts.
|
|
13
|
+
Refresh primary docs via Context7 and MicrosoftDocs/Azure documentation tools;
|
|
14
|
+
don't inspect accounts, install integrations or run examples to check freshness.
|
|
15
|
+
|
|
16
|
+
A targeted fix/source refresh is **not a full audit** and does not clear the due
|
|
17
|
+
date. Only an explicitly completed full review with dated evidence and approval
|
|
18
|
+
may update the ledger and advance to the next June 1 / December 1. No helper
|
|
19
|
+
performs that update. Reminder isn't a calendar/external notification or memory.
|