/archon-upgrade Step 6's probe is non-repeatable, and its cleanup instruction is wrong on 0.7.0

Two defects, one step, both measured (2026-08-25 proof run, Archon 0.7.0)

1. Fixed probe remote names poison the next probe on the same machine. ~/.archon/archon.db (remote_agent_codebases) keys a codebase by remote URL and stores a default_cwd. A prior probe's row (created 2026-08-23) pointed at a deleted scratchpad path; the next probe with the prescribed fixed names failed verbatim:

Error: Command failed: git -C /private/tmp/.../scratchpad/probe remote
fatal: cannot change to '...': No such file or directory

Archon reuses the stored default_cwd and ignores the actual cwd. Step 6's closing paragraph says to leave the row as "one machine's junk" — measured wrong: the row is not inert, it breaks the feature it belongs to. A run-unique suffix on the remote names worked first try.

2. The cleanup list is incomplete and its stated reason does not describe 0.7.0. Step 6 names only ~/.archon/workspaces/<owner>/<repo>/; a failed probe also leaves a workspace dir under the unmodified probe name. And the stated reason — "so a probe stops showing in archon isolation list" — is false on 0.7.0: that command prints "No codebases registered" while six rows sit in the DB.

Acceptance criteria

• Step 6 prescribes run-unique probe remote names (or instructs deleting the DB row), and says why: the row's default_cwd is reused, keyed on remote URL.
• The cleanup instruction covers every artefact a failed probe leaves, and its stated reason matches measured 0.7.0 behaviour.
• ADR-0035 amended per the dated-blockquote convention.

Context

Third finding from the same run, for whoever re-runs the trap check: a naive recursive scan for type: reports ~100 false violations — every node's output_format is a JSON Schema where type: is legitimate. The check must scope to node mappings under nodes:. Worth a sentence wherever the trap check is described.

Review the /archon-upgrade Step 6 text and ADR-0035, then compare their probe naming and cleanup guidance with the documented Archon 0.7.0 behavior. Done means the instructions cover repeatable probes, all failed-probe artifacts, the observed cleanup reason, the dated ADR update, and the scoped trap-check note.