Repository navigation
v1.3.0 - Stable rebuilt line
First Stable Release
v1.3.0 is the first stable release of the rebuilt line. It brings together the
safer upgrades from 9024, the default-settings fixes from 9025, and the new quick
upgrade guide. Technical and research commands, adapters, and skills remain
available. Installing, updating, and linking do not require Kilo.
Upgrade
Follow the Windows and macOS upgrade guide
for older installations, fresh installs, project refresh, and removal.
On v1.2.0.9024 or newer, run this from your home folder, not a project:
cg-update v1.3.0
Open a new terminal. In each project, keep its adapter selection with
--platforms on both NEW cg-link commands. For a Copilot-only project:
cg-link --check --platforms copilot
cg-link --platforms copilot
Without --platforms, every adapter is linked. Review any reported manual
action. Use the explicit version: cg-update latest follows main, not the
GitHub Latest release.
On older versions, follow the guide's one-time migration using a fresh
v1.3.0 clone. Keep the old installation backup and the printed rollback
command. Do not run the old updater or linker first.
Safer Project Refresh
- Migration keeps the old installation in a sibling backup, installs at the
original path, and pins the chosen version. cg-link --checkis read-only. Edited, unowned, and user-added files are
preserved for review rather than silently replaced.- The one-time legacy Copilot instructions transition saves original bytes in
.github/copilot-instructions.md.pre-9024.bak. Review and merge your custom
instructions from that backup. - PATH warnings explain how to use the new installation instead of an old
command that takes precedence. - Older
compound-gpid.local.mdfiles containing notes but no settings block
use defaults; an initial UTF-8 BOM is accepted. Your file is not rewritten.
Run/cg-setuplater if you need settings. - Repeated linking removes duplicate managed
.gitignoreentries and obsolete
internal copies.
Tested Coverage
Windows and macOS CI fixtures cover migration from v1.1.11 and
v1.2.0.9021, updates through the installed 9024 updater, older-updater
recovery, and the published quick-guide commands. They check backups, preserved
user files, default settings, pins, read-only checks, and repeat linking.
Required gates also run native Python and Pester tests on both platforms.
These are isolated fixtures, not proof for every historical installation or
a real Kilo host. See the release-preparation PRs and CI workflow runs for
check results.
Known Limits
- Migration supports standalone Git clones, not worktrees or linked installation
paths. Existing backups or multiple installations can require explicit
selection or recovery. Local installation edits stay in the backup, not merged. - Rollback restores the installation, not project changes or every PATH/profile
write. Keep reviewed project backups. - Windows PowerShell 5.1 long-path copy/unlink limits remain. Use short
installation paths; do not remove user files to force success. - Keep blocked or preserved files and resolve the reported manual action.
Do not delete adapter folders or use unlink to bypass conflicts.
Publication
Release payload dates identify the payload snapshot, not the GitHub publication
time. See the GitHub release page for publication status and timestamps. The
GitHub Latest designation is managed separately by the owner.