Install focused Trail skills across major coding agents

[forhappy]

What

• replace the broad checked-in use-trail bundle with five focused, independently triggered skills: trail-lanes, trail-workspace, trail-agent-tasks, trail-integrations, and trail-recovery
• add workspace-independent trail install <agent> commands for Codex, Claude Code, GitHub Copilot, Gemini CLI, Cursor, Windsurf, Cline, Roo Code, Kilo Code, OpenCode, Amp, Kiro CLI, and Qwen Code
• install into each agent's documented user-level Agent Skills directory, with product-name aliases, XDG support where applicable, dry-run, complete-suite preflight, idempotent updates, ownership manifests, local-edit protection, and atomic per-skill replacement
• document the seed-lane pattern for concurrent agents to share verified immutable environments while keeping source, build outputs, dependency uppers, secrets, services, and scratch state private per lane
• pin prolly-map 0.6 and prolly-store-sqlite 0.4 in Cargo.lock, and align Trail's exact schema-v1 validator with the 0.4 node encoding layout

Agent support boundary

The supported list is based on a concrete compatibility contract: a major coding agent must document a durable personal SKILL.md discovery directory and on-demand skill loading. Trail deliberately does not translate these skills into always-loaded rules for agents that lack native Agent Skills support. That keeps the packages portable and preserves progressive disclosure.

Target	User-level skills root
codex	$CODEX_HOME/skills or ~/.codex/skills
claude	~/.claude/skills
copilot	~/.copilot/skills
gemini	~/.gemini/skills
cursor	~/.cursor/skills
windsurf	~/.codeium/windsurf/skills
cline	~/.cline/skills
roo	~/.roo/skills
kilo	~/.kilo/skills
opencode	$XDG_CONFIG_HOME/opencode/skills or ~/.config/opencode/skills
amp	$XDG_CONFIG_HOME/agents/skills or ~/.config/agents/skills
kiro	~/.kiro/skills
qwen	~/.qwen/skills

Skill suite

• trail-lanes: concurrent lane lifecycle, inherited environments, claims, managed commands, readiness, handoff, and merge preparation
• trail-workspace: initialization, status, record/history/diff, provenance inspection, branches, checkout, and explicit Git export
• trail-agent-tasks: sessions, turns, traces, approvals, gates, leases, and handoff-oriented task evidence
• trail-integrations: structured CLI output plus HTTP, MCP, ACP, native hooks, and daemon routing
• trail-recovery: doctor/fsck, backup/restore, stale or dirty lanes, interrupted operations, and safe recovery escalation

Compatibility

prolly-store-sqlite 0.4 adds an encoding discriminator and changes the prolly_nodes table shape. Trail remains schema v1 with no migration path, so an existing workspace created with the earlier node layout fails closed and requires backup plus trail init --force --from-git.

Validation

• cargo test --workspace --locked
• cargo check --workspace --locked
• cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
• cargo test -p trail --lib agent_skills::tests --locked
• cargo test -p trail --test e2e agent_skill_install --locked
• cargo fmt --all -- --check
• git diff --check
• skill-creator quick_validate.py for all five bundled skills
• JSON validation for all five skill evaluation sets

All Cargo commands used a dedicated target directory under /Volumes/Workspace/crabbuild-target. Concurrent unstaged Colima runtime work in the primary checkout was preserved and excluded from these commits.