azure-samples/akri-connector-builder

Mark every agent-generated connector file with a format-safe made-with-AI notice and verify that source, configuration, schemas, and tests remain valid. Use after adversarial convergence and before optional Docker Desktop live testing or session close.

Implement a real SDK-backed release vertical slice, then complete selected capabilities and unit tests from specs and invariants. Use in the AKRI-CONNECTOR-BUILDER pipeline after scaffolding.

Compare implemented source against all specs for mismatches, gaps, and API deviations and fix them. Use in the AKRI-CONNECTOR-BUILDER pipeline after core implementation.

Audit source against all specs after refactoring and optimization. Use before connector metadata authoring, security review, and local validation in the AKRI-CONNECTOR-BUILDER pipeline.

Run the final verified connector in Docker Desktop, verify selected behavior and per-resource runtime health with a read-only MQTT observer, and leave the containers running for user validation. Use after AI notice verification for the startup-selected CreateConnectorE2EAndRunLocalTest intent.

Run a completed Akri connector against the anonymous endpoint and schema-valid CRs from Test Environment Authoring, using MCP lifecycle tools. Use after aio-connector-test-environment and before documentation.

Derive, write, and validate connector-metadata.json against the AIO 11.0-preview schema after final code conformance. Use before security and local integration validation in the AKRI-CONNECTOR-BUILDER pipeline.

Improve performance with evidence-based, behavior-preserving changes, one at a time. Use in the AKRI-CONNECTOR-BUILDER pipeline after readability refactoring.

Improve readability with behavior-preserving refactorings, one at a time, keeping tests green. Use in the AKRI-CONNECTOR-BUILDER pipeline after the implementation cross-check.

Create an Akri connector workspace with the MCP create-connector tool, then generate compilable source scaffolding from protocol specifications and confirmed intake requirements. Use as the first step of the AKRI-CONNECTOR-BUILDER pipeline.

Review connector security, validated metadata, and source; fix compatible vulnerabilities and produce SECURITY-REVIEW.md. Use after metadata authoring and before Test Environment Authoring.

Create accurate as-built technical specifications for the finished connector after end-user documentation. Use before adversarial convergence and optional Docker Desktop live testing in the AKRI-CONNECTOR-BUILDER pipeline.

Prepare an anonymous protocol test endpoint and matching schema-valid Device and Asset CRs for local connector testing. Use after security review and before Local Integration Validation in the AKRI-CONNECTOR-BUILDER pipeline.

Produce grounded end-user documentation under user-docs/ after code, conformance, security, and local runtime validation are complete. Use before technical documentation in the AKRI-CONNECTOR-BUILDER pipeline.

Author deterministic Helm chart and CNAB source artifacts for an Akri connector Azure Marketplace container offer. Validate local structure and produce an explicit handoff for external CPA, Marketplace, and deployment validation.