v1.6.2

ash_replicant 1.6.2 — the Replicant 1.4.2 lock move: 9.6 plugin-decoder snapshot back-fill works.

• Release lock resolved to Replicant 1.4.2 (tar sha256 aa150113…8d56e, verified against the Hex release API); the >= 1.4.0 and < 2.0.0-0 requirement is unchanged and the exact-floors CI cell keeps proving the floor.
• Replicant 1.4.2's single library change (verified against the v1.4.1…v1.4.2 bytes — query_builder.ex alone) admits PostgreSQL 9.6's two-part exported-snapshot name: snapshot: true on a 9.6 pglogical/wal2json source — inside the supported matrix — previously failed its back-fill fail-closed (:snapshot_failed → :snapshot_incomplete, delivering nothing) and now completes.
• No adapter code changes: the snapshot machinery is decoder-invariant and no lib/ code references the snapshot name. The 9.6 snapshot evidence is delegated to upstream's connected leg, which 1.4.2 itself adds (ADR-0026 amendment); ADR-0002 carries the lock-move note.
• The lock version is tied out across the release-contract checker, its self-tests, and the README/CONTRIBUTING/AGENTS lock references.
• Verified: prepush battery PASS on the released tree (structural 1006/310 excluded, live 1313/3 excluded, drift gate, dialyzer, docs, hex.build); decoder lanes 3/3 on a cluster-hosted PostgreSQL 9.6.24; CI run 37129888813 all nine cells green on this head.