Repository navigation
mega2 v0.43.0 — legacy Agent Capture retirement (minor)
mega2 v0.43.0 — legacy Agent Capture retirement (minor)
This minor release completes the legacy Agent Capture retirement family
(MTR-26, MTR-27, MTR-28, MTR-31, MTR-32, MTR-35, MTR-57) and prepares the
guarded, operator-run removal of the legacy database tables (MTR-29).
Removed
- The legacy Agent Capture HTTP surface (
/api/v1/agent_capture/*) is no
longer mounted; every former path answers404. [agent_capture]configuration andMEGA_AGENT_CAPTURE__*environment
overrides are rejected by the loader; use[traces]instead.- The legacy Capture runtime, storage, entity models and the
ObjectNamespace::Agentvariant are gone. - The
agent_tenants/agent_repo_pathscapture events and their
event-filter entries are removed; unknown storage-event targets now fail
closed.
Added
mega2 traces prepare-legacy-capture(freeze / preflight /
prepare-roles / revoke-dml) and the wired
mega2 traces purge-legacy-captureactions
(fence / inventory / delete / drop) with a maintenance-only migration
ledger.- Additive migration
m20261111_000100_trace_legacy_fence_schemacarrying
the legacy writer fence and maintenance receipt schema.
Operator notes
- Legacy Capture data is not deleted automatically. Stop the old
writers, freeze the maintenance journal, delete the frozen inventory, and
only then deploy this release and run
mega2 --config <config> traces purge-legacy-capture --action drop .... - Regular startup never runs the maintenance DROP.
[traces]stays opt-in and requires a persistentserver_id.
Compatibility
- The traces v1 protocol (
libra-traces/v1), its HTTP/SSH transports and
the fixedTracesProtocolLimitsbudgets are unchanged. - Ordinary Git, LFS, OCI and artifact behavior is unchanged.