Evidence record / paperclip

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-paperclip-october-13-canary-can-replace-a-restricted-checkout-conflict-with-an-authorized-remote-clo

October 13 canary can replace a restricted checkout conflict with an authorized remote clone. A fresh task using an implicit project default can clone the authorized remote to a separate company/task source when the project checkout contains another task restricted workspace. Current source ACLs and the run Git identity still apply. It excludes low-trust review, reused workspaces, explicit/ambiguous old bindings, pinned branches, task-independent branch templates and local-only repositories. The fallback neither grants access to the restricted checkout nor copies unpublished local changes.

Channel: preview-or-beta (2026.1013.0-canary.16; absent from stable, beta and October 13 nightly). Half: capability. Date: 2026-10-13.

Operator consequence: Trial blocked fresh-task admission with a disposable remote and verify the selected branch/source. Keep unpublished work in its original checkout. This can remove a manual checkout-repair interruption while retaining privacy; it is not a recovery method for uncommitted files.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-paperclip-october-13-canary-can-replace-a-restricted-checkout-conflict-with-an-authorized-remote-clo

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact