Record new-logger activation timestamp in docs and analysis constants #9

Manually merged

marvin8 merged 1 commit from fix/issue-8-logger-activation-note into main

2026-09-09 03:56:50 +00:00

agent-pi commented

2026-09-09 03:54:48 +00:00

Collaborator

The hardened logger went live 2026-09-09 13:52:03 AEST (03:52 UTC) — first connect marker confirms it. Two small notes so the boundary is durable:

analyze.py: new DEPLOY_LOGGER_METADATA constant alongside DEPLOY_IRR10_ONLY_GATE, same comment style, ready for before/after splits.
AGENTS.md: Logger metadata bullet records the activation time and notes that field presence (_age_s in the record) is the reliable discriminator, not dates.

Docs + constant only, no behaviour change; both test suites green.

Closes #8

The hardened logger went live 2026-09-09 13:52:03 AEST (03:52 UTC) — first connect marker confirms it. Two small notes so the boundary is durable: - `analyze.py`: new `DEPLOY_LOGGER_METADATA` constant alongside `DEPLOY_IRR10_ONLY_GATE`, same comment style, ready for before/after splits. - `AGENTS.md`: Logger metadata bullet records the activation time and notes that field presence (`_age_s` in the record) is the reliable discriminator, not dates. Docs + constant only, no behaviour change; both test suites green. Closes #8

agent-pi added 1 commit

2026-09-09 03:54:48 +00:00

📝 record new-logger activation timestamp (2026-09-09 13:52 AEST) 50a55c15c7

analyze.py gains DEPLOY_LOGGER_METADATA alongside the existing
deployment-events constant; AGENTS.md Logger metadata bullet notes the
activation time and that field presence, not dates, is the reliable
split signal.

Closes #8