sec-default: collector records continue past the user tier - #97688

Summary

TLDR: where an organization seats sec-default, a person's plugin can no longer drop or rewrite records sent to its collector.

telemetry.log for the collector's stream now continues past the user tier, as classic.* and settings.read do. The organization's own prepend and append plugins still may hook it.

Notes

The row is one line in hooks/register.ts: on('telemetry.log', { to: 'collector' }, ($, e, next) => next.to(e, 'append')). The matcher is the literal stream, so the anthropic stream is not touched.

Inert in a CLI whose own event records do not travel this event: there the row meets only what a plugin logs through $.telemetry.log. It takes effect with the release that routes the CLI's own collector records through telemetry.log, and merges after that release.

Test Plan

• mods/sec-default/tests/register.test.ts: the new case "a collector record passes over the plugins the person installed" loads a user-tier plugin that denies one record and marks every other one edited, logs two records, and expects both to arrive as logged; with the row taken out, that case is the one that fails
• the mod's tests pass 14 of 14 at this branch's head
• README: the row in the table, and the event in "What it hooks"