Mega2: second-generation, Git-compatible monorepo engine built for AI agents. Trunk-based Git storage and hosting in Rust (Postgres + S3-compatible object storage), with optional Agent Session Capture, Git LFS, build artifacts, and an OCI registry.
Repo gitmono-dev/mega2, read from GitHub 11 min ago. gitmono-dev has not joined Take My Repo.
与 megaui 协同发布的同名版本(ER-08):版本号随 megaui 协同递增。本版本完成发布门禁引导的最后一张卡(megaui plan-20261118 FSL-39),没有运行期行为变化。
.github/scripts/release-gate.mjs(与 megaui 逐字节相同):校验两仓同名 tag 解引用后,分别等于各自已核验的 main HEAD,并在判定结束前再读取一次两仓的 HEAD。对方 tag 返回 404 时,按有界串行槽位轮询(第 0 至 120 秒,最多 9 次,使用单调时钟);其它错误一律直接拒绝(fail-closed)。Cargo.toml / Cargo.lock:版本 0.43.1 → 0.43.2。release-gate 会在约 2 分钟内自动等待对方 tag 出现。v0.43.2 同名同发。与 megaui 协同发布的同名版本:自本版本起,mega2 版本号随 megaui 协同递增(ER-08,两仓同一稳定版本号)。本版本只包含发布门禁引导(megaui plan-20261118 REL-01),没有运行期行为变化。
AGENTS.md:ER-08 双仓同版本发布细则修订(FSL-38)。.github/workflows/repository-gates.yml:增加 push: branches: [main] 触发,使 main HEAD 有可核验的质量门(FSL-22)。.github/scripts/release-gate.mjs(新,与 megaui 逐字节相同):docker.yml 的 release-gate job 改为运行此脚本,核对两仓同名 tag 与两仓指定质量门(megaui ci.yml、mega2 repository-gates.yml)在当前 main HEAD 上成功,失败即关闭(FSL-29、FSL-71、FSL-72、FSL-43)。Cargo.toml / Cargo.lock:版本 0.43.0 → 0.43.1(FSL-66)。为使 repository-gates.yml 在自托管 runner 上稳定通过,本版本另含以下只影响测试与 CI 的提交,不改变生产行为:
b1154f7 test(snapshot):测试构建中 chunk-map 与 retention 内存预算按测试 schema 隔离(生产仍为进程级共享池)。99cc853 test(snapshot):测试中强制 reader 到期的间隔由 20 ms 改为 1 s,并改为等待数据库确认到期。21e44a4 ci(repository-gates):仓库测试限制为 4 个线程(已被下一项取代)。7f63b20 ci(repository-gates):改用 cargo-nextest 测试分组运行,其中依赖 PostgreSQL 的库测试最多 6 个并发,各集成测试二进制串行执行。main HEAD 上成功。v0.43.1 同名同发。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).
/api/v1/agent_capture/*) is no404.[agent_capture] configuration and MEGA_AGENT_CAPTURE__* environment[traces] instead.ObjectNamespace::Agent variant are gone.agent_tenants / agent_repo_paths capture events and theirmega2 traces prepare-legacy-capture (freeze / preflight /mega2 traces purge-legacy-capture actionsm20261111_000100_trace_legacy_fence_schema carryingmega2 --config <config> traces purge-legacy-capture --action drop ....[traces] stays opt-in and requires a persistent server_id.libra-traces/v1), its HTTP/SSH transports andTracesProtocolLimits budgets are unchanged.Add the traces prepare-legacy-capture maintenance command with freeze, preflight, prepare-roles, and revoke-dml actions. It connects the existing maintenance drivers to the explicit CLI and preserves the existing purge-legacy-capture actions.
The new command requires an explicitly named configuration, checks the existing schema without running migrations, and closes its maintenance database connection on success and failure. It prepares provenance, scope, and role receipts; it does not delete Capture objects or tables. Old-writer restart denial, live DB/object write denial, table removal, and H6 still require separate deployment evidence.
The final .149 local C2 tree passed all five gates: nightly formatting, strict Clippy, the complete test suite, cargo build, and cargo build --tests. The test run completed 24 result groups with 3,347 passed, 0 failed, 3 originally ignored, and 0 filtered. It completed in 10,085.671 seconds within the six-hour monitor boundary. The machine-readable receipt is target/20261015/v0149-c2-20261112/success-receipt.json (SHA256 ec618d751da23e5917f90bb88d87dd32147c7f76909f86eb514558b74c758e1d).
This validates the local release tree. Main/tag Docker workflows and the live Capture retirement/H6 acceptance remain separate follow-up checks.
Repair legacy Capture write fencing in PostgreSQL schemas other than public.
The fence now reads the persistent barrier belonging to the triggering table. Quoted schema names work, caller-controlled search paths cannot select a shadow fence, and missing fence storage refuses writes. Non-Capture event JSON retains its existing tenant_id: null field; a contradictory test assertion is corrected.
A forward migration replaces the fence function while preserving its owner, privileges, journal and fence rows. No configuration change is required. The down migration intentionally leaves the repaired barrier in place. Already retired Capture tables are not recreated.
The final .148 C8 tree passed all five local gates: nightly formatting, strict Clippy, the complete test suite, cargo build, and cargo build --tests. The test run completed 24 result groups with 3,344 passed, 0 failed, 3 originally ignored, and 0 filtered. The monitor observed one runner, exit code 0, and no timeout. The machine-readable local C receipt is target/20261015/v0148-c8-20261112/success-receipt.json.
This validates the local release tree. The main/tag Docker runs and deployment retirement/H6 acceptance are separate follow-up checks.
This patch repairs a maintenance prerequisite. It does not complete deployment retirement, delete objects or drop legacy tables. Those operations and H6 retain their separate deployment acceptance requirements.
This recovery Release documents the existing annotated v0.42.147 tag at commit 1f47bb42a597f78a0192d664258d9df159df0b7c. It does not move the tag or backdate acceptance. The existing SSH signature passed local ssh-keygen -Y check-novalidate verification on November 11, 2026. That verifies the signature mathematically; GitHub still reports unknown_key, and no key registration or identity trust was changed.
The tagged tree contains breaking legacy Capture removals despite its historical patch version. Remove [agent_capture], MEGA_AGENT_CAPTURE__*, legacy Capture event names and the agent_tenants / agent_repo_paths filters before startup. The formal MTR-29 retirement minor release remains required.
Cleanup deletes only manifest-authorized legacy data; it does not migrate that data into Traces. Ordinary startup does not perform the guarded DROP. The operator must establish the writer perimeter and complete the verified purge before the explicit maintenance action. Existing Git Traces history must remain intact. See the retirement contract.
2026-11-09T21:30:31Z.linux/amd64, native linux/arm64, and the multi-platform manifest. It completed at 2026-11-09T21:48:41Z.MTR-46's actual old-image write-denial and deployment-perimeter acceptance, and MTR-29's minor release and H6 cleanup receipts, remain separate work. A probe's image-digest label alone does not execute that image. Follow-up FIX-MTR-34 / FIX-MTR-35 and FIX-MTR-33 are not part of this tag. Creating this Release does not complete those tasks or the two plans.