memory: note auto-mirror dual-push setup

memory/tangled-mirrors.md

@@ -12,10 +12,13 @@ metadata:
 - `git@tangled.org:did:plc:3nogfd4smhmbrv4wo6kl7zg2/agent-orchestrator`
 - `git@tangled.org:did:plc:3nogfd4smhmbrv4wo6kl7zg2/project-orchestrator`
 
-Both repos have a `tangled` remote (origin stays `git.autonomic.zone`). Re-mirror after pushing to
+**Auto-mirror is configured:** `origin` in both repos has TWO push URLs (git.autonomic.zone AND
-origin with: `git push tangled main` (and `git push tangled --tags`). Tangled's git SSH wants **DIDs,
+tangled), so a plain `git push origin <branch>` fans out to both — no separate step. Set up with
-not handles**, in the path; the `Welcome to Tangled's hosted knot!` line is just a banner (not an
+`git remote set-url --add --push origin <primary>` then `… --add --push origin <tangled>` (the first
-error).
+`--add` replaces the fetch-url default, so the primary must be re-added too). A standalone `tangled`
+remote also exists for explicit `git push tangled …`. Tangled's git SSH wants **DIDs, not handles**,
+in the path; the `Welcome to Tangled's hosted knot!` line is just a banner (not an error). If tangled
+is unreachable, `git push origin` reports a failure for that target only.
 
 Auth: dedicated key `~/.ssh/tangled-ed25519`, registered to the tangled bot account
 `notplants-bot.bsky.social` (the bot's own DID is `did:plc:qfngkejlw4ghji2myc73hbdh`); `~/.ssh/config`