Consolidate the local Skill installation lifecycle

[miniLV]

This was generated by AI during triage.

What to build

Consolidate repository-managed Skill inspection, installation, repair, selective pruning, and safe removal behind one local lifecycle interface.

The setup UI, agent-first setup, shell entrypoints, status reporting, and uninstall flow should reuse the same ownership and target rules while preserving their current user-facing behavior.

Acceptance criteria

• One interface owns target discovery, resolved-link validation, repository ownership, safe replacement, selective pruning, and removal behavior.
• Codex and Claude targets use the same lifecycle semantics.
• Setup, status, repair, and uninstall callers report consistent results for the same filesystem state.
• Repeated installation is idempotent.
• Repository-managed stale links can be repaired without deleting unrelated or user-managed files.
• Isolated-home tests cover missing, valid, stale, copied, unrelated, selected, and deselected target states.
• Existing setup and uninstall user behavior remains compatible.
• The full test suite and strict Wiki lint remain green.

Blocked by

• Expose the read-only memory Skill to Claude in Step 06.

[miniLV]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Give every setup surface one shared local lifecycle contract for repository-managed Skills.

Current behavior:
Status inspection, link ownership, replacement, pruning, setup, and uninstall rules are implemented across multiple shell and JavaScript paths. The behavior works, but fixes must be repeated and can drift across operating systems and agent targets.

Desired behavior:
One local lifecycle interface owns inspection and mutation semantics. Web setup, agent-first setup, shell commands, and uninstall use it as callers or adapters while preserving existing visible behavior.

Key interfaces:

• Lifecycle inspection — reports target state and repository ownership consistently.
• Lifecycle mutation — install or repair selected targets, prune deselected managed targets, and remove only owned targets.
• Machine-readable result — lets setup UI and command-line flows present the same facts.

Acceptance criteria:

• Every caller gets the same target state for the same filesystem fixture.
• Codex and Claude share ownership, installation, repair, and pruning semantics.
• Valid links are idempotent and stale managed links are repairable.
• Unrelated links, directories, copied user content, and unmanaged Skills are preserved.
• Isolated-home tests cover supported operating-system path behavior.
• Existing setup and uninstall behavior remains compatible.
• Full tests and strict lint remain green.

Out of scope:

• Adding another agent target or scheduled runner.
• Changing query or memory semantics.
• Redesigning the setup interface.