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-github-skill-packages-ship-in-stable-automatic-future-instruction-refresh-reaches-canary

GitHub skill packages ship in stable; automatic future instruction refresh reaches canary. Stable imports commit-pinned complete GitHub skill packages with supporting files and executable modes, manual refresh and retained active/pinned content. Import does not run scripts, hooks, installs or builds. October 13 canary adds project-attachment import and roughly five-minute automatic refresh. New executions use the latest installed version; resumed/pinned executions keep their snapshot. Existing manual sources gain automatic updates; legacy project attachments require explicit adoption. The pinned acceptance record reports a real GitHub marker update used by an unchanged routine, plus authorization/restart checks. That is vendor-recorded acceptance, not a new run here.

Channel: mixed (manual packages tagged-release; automatic refresh preview-or-beta, canary only). Half: both. Date: 2026-10-06 (manual packages); 2026-10-13 (automatic refresh).

Operator consequence: Review repository ownership, selections and automatic-update preferences before adopting canary. A repository commit can then change future instructions without a manual Refresh click. Per-execution snapshots support reproducibility; they do not mean every upstream update received a human approval. Keep stable manual-refresh behavior separate from the canary automation.

Receipt

Finding metadata

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

Finding ID: 2026-10-13-paperclip-github-skill-packages-ship-in-stable-automatic-future-instruction-refresh-reaches-canary

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact