Adopt the CLI-scaffold-parity component baseline (#4)

[mbreissi]

Summary

Full remediation for #4 (file-replicator's leg of the org-wide CLI-scaffold-parity baseline sweep). file-replicator is a sink, not a southbound adapter, so only the cross-cutting items 1-6 from #4 apply — no sb/* verbs, no southbound_health, no panel trio. Naming, dependency-pin shape, coverage-seam discipline, and Diátaxis docs already met the baseline per #4's own gap analysis and are unchanged here.

Per the resolved scope decisions in the master remediation plan: full P0+P1+P2, Cargo.lock committed (SD-B), and the Apache-2.0/BUSL-1.1 license mismatch (#2) fixed inline.

Per-item checklist (against #4)

• P0-1 — commit Cargo.lock. Dropped the /Cargo.lock gitignore rule and its stale rationale comment; committed a lock regenerated against the pinned git rev with no local .cargo [patch] override active.
• P0-2 — license → BUSL-1.1 (Fixes #2). Cargo.toml's license field and the README's license line now both declare BUSL-1.1, matching the shipped LICENSE.
• P1-3 — config.schema.json. Authored against src/config.rs/docs/reference/{configuration,destinations}.md: component.global (defaults, limits, onPermissionError — what edgecommons component validate actually checks) plus a full $defs/instance reference covering ingress/readiness, all seven egress backends, schedule, completion, retry, and priority. Validated against the shipped test-configs/config.json instance and a synthetic instance exercising every backend/variant, plus a negative case.
• P1-4 — .github/workflows/deploy-docs.yml. Added verbatim from modbus-adapter — ci.yml paths-ignores docs, so doc-only pushes were not refreshing the site.
• P1-5 — root README.md rewrite. Removed the dev-diary "Implemented through P6... P7 remains undone... docs lag" narration (which also contradicted docs/README.md's own "validated against src/"); replaced wholesale with present-tense current-state text. The phase history already lives in DESIGN.md §21.
• P2-6 — CLAUDE.md → baseline import shape. Was a near-duplicate of AGENTS.md; now a short header + @AGENTS.md import + this component's own local-dev notes.
• P2-7 — recipe sample-value sweep. Replaced the shipped Greengrass recipe's tags: {appId: "Test", site: "Chantilly"} with neutral "CHANGE_ME" placeholders.
• Docker: bump the Rust build base off 1.85 (can't build current Cargo.lock) #3 coordination — Docker build base. rust:1.85-slim could not build the correctly git-resolved locked tree at all (AWS SDK crates need rustc 1.94.1+, crc-fast needs 1.89+); bumped to rust:1.96-slim, matching config-component's precedent cited in Docker: bump the Rust build base off 1.85 (can't build current Cargo.lock) #3. rust-version MSRV in Cargo.toml is untouched.

A bug the validation work turned up and fixed along the way

Two issues surfaced only by actually running the validation gates, not part of the original checklist:

1. The first committed lock was wrong. This worktree lives nested inside the main file-replicator checkout (file-replicator/.claude/worktrees/...), and Cargo's config discovery walks every ancestor directory for a .cargo/config.toml. The main checkout's own gitignored local-dev [patch] override was therefore still in scope from inside the worktree, so the first lock generation silently recorded edgecommons as a path dependency (version = "0.3.0", no source) instead of the pinned git rev — unresolvable from a fresh clone or CI. Caught by cloning to a directory outside that ancestry and comparing; regenerated correctly there (only the edgecommons package's own entry changed — every transitive dependency was already identical, since the override doesn't touch the rest of the graph).
2. test-configs/config.json's heartbeat.targets[] predates the heartbeat→state UNS migration (the canonical schema now takes heartbeat.destination; recipe.yaml already used the current shape). This was failing edgecommons component validate outright. Fixed to destination: "local".
3. The Dockerfile's own comment promised GITHUB_TOKEN support that didn't exist — nothing in the file consumed one, so the image could not be built at all to prove out the Docker: bump the Rust build base off 1.85 (can't build current Cargo.lock) #3 fix. Wired it up via a BuildKit secret mount (--mount=type=secret), not a --build-arg/ENV (Docker's own linter flags those as leaking into image history for exactly this kind of value).

Validation evidence

All run locally (Windows, native Rust toolchain 1.96.0), using an isolated clone outside the worktree's directory ancestry so the local-dev .cargo override could not interfere:

• cargo build --locked --release --features dest-s3,dest-sftp,dest-ftps,dest-http,dest-azure,dest-gcs — green.
• cargo test --locked (same features) — all suites green, including the simulator-backed integration tests.
• cargo clippy --locked --all-targets (same features) — clean, no warnings.
• cargo llvm-cov --locked --fail-under-lines 90 (CI's exact exclusion set) — 93.41% line coverage, gate passes.
• Fresh-clone build proof: cloned the pushed branch to a directory with no .cargo/config.toml in its ancestry; cargo build --locked resolves the pinned git dependency and builds clean — proving the committed lock is fit for CI/a real fresh clone.
• edgecommons component validate (built from the cli-scaffold-parity worktree, per PR CLI scaffold parity: close the ethernet-ip-adapter dogfooding gaps across all 16 templates edgecommons#57): OK — no findings.
• Docker image build, from a fresh clone, docker build --secret id=github_token,env=GITHUB_TOKEN: builds the locked tree clean on rust:1.96-slim, no linter warnings, confirmed no token in docker history.

Deviations / scope notes

• Two small fixes (the Docker git-auth wiring, the heartbeat.targets stale test-config) were outside the issue's literal checklist but were necessary to actually prove the checklist items true rather than assert them — both are called out above rather than folded in silently.
• No live-infra gate applies to this leg (file-replicator's own validation matrix row lists none required beyond the local gates above and the Docker build).

Fixes #4
Fixes #2

🤖 Generated with Claude Code

https://claude.ai/code/session_01DxV5wFi7LCratBERVT6aiL