müde 35b0edaf27 manager_server: fetch+tag at request_apply_commit submit ... submit_apply_commit (1) queues the approval row, (2) git-fetches the manager-supplied sha from proposed into applied, pins it as refs/tags/proposal/<id>, (3) persists the resolved sha on the row via approvals.set_fetched_sha. from this point on the proposal is immutable from the manager's perspective: amends or force-pushes in proposed do not change what hive-c0re will build. fetch failures mark the row failed and surface the error to the manager so a phantom pending entry can't linger.		2026-05-15 22:57:43 +02:00
..
assets	surface agent-vs-agent port collisions (manager:8000 can't collide)	2026-05-15 22:08:19 +02:00
src	manager_server: fetch+tag at request_apply_commit submit	2026-05-15 22:57:43 +02:00
Cargo.toml	Phase 7b: broker broadcast + dashboard SSE message-flow tail; pkgs.git in module	2026-05-15 00:13:34 +02:00