Release 1.0.2

[MongLong0214]

Five fixes have been on main since v1.0.1 and none has reached anyone.

#696  the hook pinned the release it was installed from
#698  install.sh never installed the Codex plugin; install.ps1 did
#700  a failed Codex integration reported healthy and exited 0
#702  documents claiming more than the product does
#704  the PowerShell 5.1 floor documented but not enforced

Four are at the installer and hook boundary, and that boundary has exactly one
delivery mechanism. Measured at v1.0.1: re-installing with main's install.sh
changed nothing, because the code being installed is the released binary.

#700 is the one a user meets first. Registering Codex is two steps, and the
installer called the host healthy when the second failed — it said plugin step
failed in its detail and exited 0, because ok is computed from the field
rather than the sentence. That defect was introduced in #698 while fixing #697,
and found by the closeout review.

The bump

Thirty-eight pins across nine files. dist unchanged, canonical digest
identical — ca608927. The version is read from package.json at runtime rather
than compiled in; rebuilt through the canonical builder and verified rather than
assumed, as with the two releases before it.

The installers and READMEs carry the tag in URLs that resolve only once the tag
exists, so this is one commit and the tag goes on it.

After publishing

docs/RELEASE-GATE.md §6b and §6c apply: read the check runs at the commit the
merge creates, and install over v1.0.1 rather than fresh. The specific
readbacks this release needs:

commitlore --version                 → 1.0.2
commitlore hooks install             → repoints commitlore.bin at <data-root>/current
commitlore doctor                    → hook/CLI identity agrees
codex plugin present on macOS/Linux  → the #698 fix, absent before

Baseline measured before the release, for comparison: CLI 1.0.1, hook pinned
at …/v1.0.1/dist/commitlore.mjs, doctor 12 ok / 6 warnings / 0 failed.

Not in this release

#691 — install.ps1 wires hosts directly as well as delegating. Removing the
duplicates needs a Windows machine with agents installed; CI cannot substitute,
because its runners have none and every host reports notDetected there.

[github-actions]

CommitLore — record lint

Trailers: clean — 2 commits in origin/main..a3e04dbf9e36cefb1bd4f5ae4318a5690d86616d
Active constraints: not read — commitlore: git log --follow accepts exactly one pathspec, so renames are not followed for 11 paths; query one path at a time to follow its rename chain (11 changed paths)

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}