fix(templates): bind native authorization to fixed-template bytes - #53

Summary

• Bind native fixed-template authorization to raw source bytes, rendered UTF-8 bytes and raw destination bytes (null when missing), without content in observations.
• Check before the first mutation and before the template batch; write the exact validated capture while preserving ensure skips, replace-always-write behavior, target order and platform report paths.
• No lifecycle/sync/protection activation, configuration flags, API Expose a read-only repository planning API with an injected command backend #49, version bump or release.

PR type

• Bug fix — type:bug
• New feature
• Documentation only
• Code refactoring
• Maintenance/tooling
• Breaking change

Changes

Review scope: 5 paths, 372 additions / 24 deletions = 396 combined lines.

Validation

• Focused checks passed: 15/15 in LF and physical CRLF.
• Documentation and configuration updated when needed (docs changed; configuration schema unchanged).

Meaningful native CLI RED with bootstrap unwired: 15 tests, 8 passed / 7 behavior failures; all six delivered tests passed. Initial wired 14/15 exposed an incorrect expected skipped-label record in the late partial-report test. The complete expected record was corrected without removing assertions; focused GREEN is 15/15.

Local Node 24/Linux checks:

• Full suite: 201/201 passed in each LF and physical CRLF variant, zero failures/skips/cancellations.
• Same-rendered invalid UTF-8 source drift and destination byte drift: all four assets in ensure/replace, early rejection and fresh approval.
• Causal early/late interleaving through an offline gh fixture; late rejection preserves earlier completed and skipped work.
• Template-absent authorization matches the legacy canonical observation shape; non-regular, missing and symlink cases checked.
• Gitleaks 8.30.1: both directory variants and all 39 locally available commits clean; four scanner fixtures pass in each variant.
• Actionlint 1.7.12: both workflow inventories and four fixtures pass in each variant.
• One npm pack: exactly 72 unique regular files, no symlinks; Source/freeze/archive bytes identical; version remains 1.1.0.
• Independent verification reproduced 396 lines, 72 hashes and its own 15-pass run; native risk/resilience/readability/reliability review approved and acknowledged.

LSP limitation: one primary active batch returned 0 diagnostics, 0 confirmed-clean files and 4 inconclusive checks. The human explicitly accepted this limitation for this candidate; it is not successful semantic type checking. Native assessment was unassessable due untracked declaration, so high-risk self-verification plus a separate independent verifier were performed; native approval did not replace functional checks.

Hosted Node 20/Windows/macOS results are pending CI, not inferred from Linux. The new source-file symlink test explicitly skips Windows; the two inherited descriptor/procfs skips remain separate. Metadata capture now reads assets even in ensure mode and rejects non-regular sources/destinations: not a behavior-neutral refactor. Batch capture does not eliminate later races, aliases, source-read races or provide global rollback. The trusted offline fixture is not a sandbox.

Contributor checklist

• Approved linked issue, nonclosing reference.
• Exactly one PR type selected: Bug fix (type:bug).
• Applicable focused/full checks run and behavior documentation included.
• Conventional commit, no Co-Authored-By trailers.
• Shellcheck and changed-skill loading: not applicable; no shell script or skill instruction files changed.
• Technical probes, failed-run evidence and verification snapshots retained outside the 72-file product/archive selection.

Linked issue

Refs #15

This unit does not complete or close #15. Remaining runtime modules, offline #15/live #17 acceptance, protection/migration and independent API candidate #49 remain separate. No merge, auto-merge, release, Root synchronization or cleanup requested.