fix: remove legacy references — Rust source + agent skills (5 files) #249

Merged
clawdie merged 1 commit from fix/remove-legacy-references-rust-and-skills into main 2026-06-28 00:10:55 +02:00
5 changed files with 8 additions and 8 deletions

View file

@ -22,7 +22,7 @@ Current layout:
## Canonical addresses
- `warden0`: `${AGENT_SUBNET_BASE}.1/24`
- `.2`: reserved compatibility slot (legacy controlplane naming)
- `.2`: reserved compatibility slot (earlier controlplane naming)
- `{agent}-db`: `${AGENT_SUBNET_BASE}.3`
- `{agent}-cms`: `${AGENT_SUBNET_BASE}.4`
- `{agent}-ollama` or `{agent}-llamacpp`: `${AGENT_SUBNET_BASE}.5` (optional)

View file

@ -58,7 +58,7 @@ Send a test message on Telegram and check `logs/clawdie.log` for the new provide
## Installing / Reinstalling pi
**IMPORTANT:** pi is published as `@earendil-works/pi-coding-agent`.
Older docs or installs may mention legacy package names; use the `pi-update`
Older docs or installs may mention earlier package names; use the `pi-update`
skill for package-rename migrations. In the controlplane jail, install from the
host's pre-built copy so the jail does not need to rebuild the multi-package pi
project:

View file

@ -7,7 +7,7 @@ description: Update the pi coding agent harness safely. Use when the operator as
Update the `pi` coding-agent harness and its pi packages/extensions with minimal disruption.
Pi is currently published as `@earendil-works/pi-coding-agent`. Older installs may still use `@mariozechner/pi-coding-agent`; treat that as the legacy package name and migrate away from it.
Pi is currently published as `@earendil-works/pi-coding-agent`. Older installs may still use `@mariozechner/pi-coding-agent`; treat that as the previous-generation package name and migrate away from it.
## Rules
@ -45,7 +45,7 @@ Record:
- current version
- global npm root
- whether `@earendil-works/pi-coding-agent` is installed
- whether legacy `@mariozechner/pi-coding-agent` is still installed
- whether the earlier `@mariozechner/pi-coding-agent` is still installed
- installed pi packages/extensions, if any
## 2. Check latest upstream release
@ -94,7 +94,7 @@ A healthy final self-check says pi is already up to date.
## 4. Rename fallback path
Use this only if `pi update --self` cannot migrate a legacy install.
Use this only if `pi update --self` cannot migrate an earlier install.
Check whether the old package is installed:
@ -162,6 +162,6 @@ Summarize:
- old version and new version
- package name used
- whether legacy package migration was needed
- whether previous-generation package migration was needed
- whether pi packages/extensions were updated
- any stale Clawdie references found for a follow-up patch

View file

@ -15,7 +15,7 @@ Keep Linux, FreeBSD, and ISO runtime inputs aligned without relying on moving
- For security-sensitive auth paths, inspect before mutating.
- Pin build inputs; do not let ISO builds depend on moving npm dist-tags.
- Prefer Node 24 across Linux and FreeBSD unless a target explicitly requires a
legacy lane.
earlier lane.
- Use repo-local `tmp/` for generated inventories and manifests.
## 1. Inventory local host

View file

@ -702,7 +702,7 @@ pub struct Pane {
pub id: String,
pub agent: String,
pub state: AgentState,
// `alias` keeps deserializing the legacy `pi_session_id` key (pre-zot wire
// `alias` keeps deserializing the original `pi_session_id` key (pre-zot wire
// format / persisted snapshots) onto the harness-neutral field.
#[serde(
default,