Synapse golden-path commands

fa synapse is the source-specific convenience layer for the reference Synapse-to-Databricks journey. Local compilation is deterministic and needs no API. Registration uses the authenticated Airlift API and the existing governed artifact action.

fa synapse inspect

fa synapse inspect --file synapse-manifest.json
fa synapse inspect --file synapse-manifest.json --json

Parses the versioned manifest, validates unique source IDs and dependency references, detects cycles, compiles embedded ADF resources, and prints scope and residue totals. Exit status 0 means the manifest can produce a bundle. Invalid schemas, missing dependencies, and cycles exit 1.

fa synapse compile-adf

fa synapse compile-adf --file TemplateForWorkspace.json --json

Compiles an ADF/Synapse ARM template into ETL IR version 1. The JSON result contains tasks, triggers, linked-service binding requirements, and residue. The compiler does not emit or retain linked-service credentials.

fa synapse plan

fa synapse plan --file synapse-manifest.json --json > synapse-plan.json

Emits application/vnd.fabric.airlift.synapse-golden-path+json. The document contains:

• source snapshot and inventory digest;
• topological dependency order;
• ETL tasks with dependencies, parameters, retry policy, and disposition;
• Databricks target-asset mappings;
• snapshot/incremental movement proofs;
• Experiments validation suites;
• agent-repairable and human-only residue;
• completion evidence for discover through modernize;
• a canonical SHA-256 bundleDigest.

The same input produces the same output and digest.

fa synapse register

fa synapse register \
  --file synapse-plan.json \
  --engagement-id <engagement-id> \
  --estate-id <estate-id> \
  --artifact-id <immutable-artifact-reference> \
  --idempotency-key <stable-key>

Validates the generated bundle and invokes airlift.artifact_register with kind plan. The command records the supplied immutable reference; it does not upload local content. Configure AIRLIFT_API_URL and DATABRICKS_TOKEN as described in remote automation.

Registration fails closed when the engagement or estate belongs to another tenant, the principal lacks artifact authority, the bundle is invalid, or the request digest does not match the idempotency key generated by the CLI.

fa synapse certification-check

Run the repository-owned, account-independent suite first:

pnpm certify:synapse

The runner writes a human-readable report and a versioned evaluator input under reports/. Check that input independently or in CI:

fa synapse certification-check \
  --file reports/f8c-synapse-evidence.json \
  --json

Exit status 0 means every stage required by the requested proof level is present, content-digested, tied to the same build and dataset, and completed before the report observation time. Missing, future-dated, wrong-build, or wrong-dataset evidence exits 1.

The account-independent request schema accepts only hermetic_proven and workspace_proven. It rejects client_proven and production_certified rather than letting a caller reinterpret local test results as production evidence.

Workspace proof additionally requires immutable evidence for the live App API, target materialization, Experiments validation, Runway release, and Temporal rehearsal. A successful App deployment alone is insufficient.