3 Commits

Include renames

Author	SHA1	Message	Date
Omar SobhandClaude Opus 5	1d554396f4	fix(delivery): four failures from the #55 trace — auth, prompts, truncation, retry ... All four were surfaced while tracing #55 and left open. Each one on its own is small; together they are why a two-line git rejection took hours to read. **1. `with_ambient_auth` failed open.** It matched one literal prefix, `https://git.redclaw.dev/`, and returned the URL unchanged for everything else with no log line. An `http://` remote, an explicit port, a different case in the host, an ssh remote, a URL that already carried userinfo — all came back unauthenticated and looked identical to success. It now returns `Authed`, which carries the URL AND why no credential reached it, and recognises the forge in every shape a remote can be written (host parsed with userinfo stripped BEFORE the port, or `oauth2:token@host` reports its username as the host — the first version of this function did exactly that and failed its own test). **2. Nothing set `GIT_TERMINAL_PROMPT=0`.** So a credential-less URL did not fail — git opened `/dev/tty`, and in a server container that surfaces as `No such device or address`, several layers from the missing token. Now set on every git invocation that can reach the network. And `push_url_for` refuses outright when the URL is on OUR forge and unauthenticated: that push cannot succeed, and letting it proceed only buys a symptom that looks like something else. **3. The truncation fix went to the wrong path.** e31688b clamped the caller, but a rejected push comes back as `Ok(Publish { error })` — the string was already cut to 300 head chars inside `git()`, so the reject reason had been dropped before the both-ends clamp ever saw it. Clamped where the output is produced, and redacted there too. **4. #55: a mission that re-clones can never push.** The branch name is deterministic per (mission, phase, iteration), so a checkout rebuilt after a retry, a container teardown or disk loss produces divergent history against its own branch, and git rejects it — leaving the work on a local branch in a directory the sweeper deletes. Reachable in normal operation, not just by deleting a checkout by hand. The escape is a NEW ref, not `--force`: forcing would overwrite whatever the earlier attempt pushed, which may be the only copy of that work, to make this attempt look tidy. The retry lands on `<branch>-<sha8>` — deterministic, self-describing in a branch list, and collision-free since divergent history is by definition a different sha. "Never force" stays a rule. NEGATIVE CONTROL, run rather than assumed: with the rescue arm disabled, `diverged_history_lands_on_a_new_branch_instead_of_being_lost` FAILS with git's real `! [rejected] ... (fetch first)` — which also demonstrates fix 3, since that whole message now survives to the assertion. The test asserts the earlier attempt's ref is byte-identical afterwards. Also measured, not read off docs: which hooks fire under `claude -p` (2.1.222, via `--settings`). SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, SubagentStop and Stop fire; TaskCreated, TaskCompleted, TeammateIdle, SessionEnd, Notification and PreCompact do not. So the agent-teams hooks Slice 3 deferred are inert on our path by construction, and `Stop` is the seam that could move `done_when` into the agent's own loop. 507 tests pass, clippy clean. Co-Authored-By: Claude Opus 5 <[email protected]>	2026-08-06 13:15:15 -07:00
Omar SobhandClaude Opus 5	9de2cf34e4	feat(auto-merge): merge additive branches, refuse everything else ... Closes the branch pile-up: a catalogue branch that only adds notes now merges into main by itself, so the work is actually in the vault rather than waiting in a branch nobody opened. Additive-only is measured from the diff, not assumed from the mission type. Three conditions, all required: the type declares additive_only, the run verified, and `git diff --name-status base...branch` contains only A entries. A research harvest that somehow rewrote a hand-written note is refused by the same check that lets its new notes through — which is the case the test pins down, asserting README.md on main is byte-identical afterwards. Renames and deletes count as non-additive. A rename is a delete plus an add and the delete half can destroy hand-written work. Unknown merge_policy values fail closed to Never. A typo must not grant auto-merge. The diff is taken against FETCH_HEAD, freshly fetched, using `...` so an unrelated commit landing on main meanwhile is not misread as ours. A conflicted merge aborts and leaves the branch for a human rather than wedging the checkout for the next run. merge_reason is always populated and surfaced in the API: a branch that quietly did not merge is indistinguishable from one never delivered. 399 tests, clippy clean. Co-Authored-By: Claude Opus 5 <[email protected]>	2026-08-03 11:33:41 -07:00
Omar SobhandClaude Opus 5	09c6496725	feat(library): clone the vault, harvest our topics, push the catalogue ... Completes the loop: the notes now land in the real vault. Topics come from what the project is actually working on — papers/dynamic-agentic- topologies.md (topology search, ADAS/Darwin-Godel/SwarmAgentic) plus the two problems this week ran into, verifying what an agent did and giving a long-running agent memory of what it covered. Never pushes to main. The vault is a live Obsidian vault a human edits and syncs; pushing to main races that sync and can lose hand-written work. Every run lands on its own branch for a human to merge, the same rule the mission delivery path was validated 20/20 under. PDFs are NOT committed. A few hundred papers is gigabytes and would make the vault painful to clone and slow to open, so they stay on the blob store shelf and the note carries the key. My own test caught me repeating this week's branch-collision bug: I named branches from the HEAD of a UUIDv7, which is a 48-bit timestamp, so two runs in the same millisecond produce the identical name — exactly what hit mission 019fc42b. Fixed by taking the tail. The test now loops 100 ids instead of sampling two (a one-shot check passes by luck whenever the millisecond ticks between calls) and additionally asserts the head-based scheme DOES collide, so it cannot rot into a no-op. Live against the real vault: 10 candidates, 1 already held, 9 shelved, 0 failed branch clawmates/library-019fc82292e8, pushed 9 notes verified on the forge, 9 PDFs verified %PDF on the shelf (the "1 already held" is cross-topic dedupe inside a single run) Co-Authored-By: Claude Opus 5 <[email protected]>	2026-08-03 08:03:14 -07:00