Flip LLP 0122 hermes design to Active (shipped via #339)

[philcunliffe]

Lifecycle-only follow-up: flips llp/0122-hermes-log-forwarding.design.md from Accepted to Active.

The hermes log-forwarding change set (LLP 0118-0125) shipped in PR #339, but the design-first Accepted -> Active flip (LLP 0016 Shipped-is-Active) did not ride the implementation PR (plan 0123 had no flip task). As a result neutral implementable kept re-surfacing the design as owed-implementation even though all code is already merged to master.

This is a one-line lifecycle move, NOT new code or a re-implementation - the diff is exactly the status header. No code, tests, or other docs change.

Change-Set: hermes-log-forwarding

[philcunliffe]

Reviewed clean.

Verified in a fresh detached worktree at 1ac5370b4799a23cedbb4c3ebf4f7f4d53015a03 (git diff origin/master...1ac5370b4799a23cedbb4c3ebf4f7f4d53015a03): the entire diff is a single lifecycle move in llp/0122-hermes-log-forwarding.design.md, one line, **Status:** Accepted -> **Status:** Active. No code, no tests, no other docs, no other lines touched (+1/-1 across 1 file, matches the PR's reported stat).

Sanity-checked that Active is the correct status per LLP 0016 (Shipped-is-Active):

• The hermes plugin implementation is present on master: hypaware-core/plugins-workspace/hermes/{hypaware.plugin.json,src/backfill.js,src/config.js,src/errors.js,src/git_repo.js,src/index.js,src/projector.js,src/source.js,src/state_db.js,src/types.d.ts,src/watermark.js}.
• PR hermes log forwarding adapter (LLP 0118-0125) #339 (the hermes implementation PR) is MERGED (gh pr view 339 --json state,mergedAt -> state: MERGED, mergedAt: 2026-07-21T01:54:32Z).

CI is green on the head commit. This is a clean lifecycle-only flip with no drift.

Reviewed-clean. Next tick readied and held for a human merge.