Deferred decisions from the skills campaign (staging model · skill-roots default · Legato naming)

[aarontrowbridge]

Important

Problem — Three decisions surfaced by the 2026-08-26 skills audit + freshness campaign that are deliberately NOT implemented overnight: they change live server behavior, shipped defaults, or product naming — human territory.
Approach — Each is framed with the evidence and a recommended direction; nothing is merged until a human decides.
Scope — three sections, three independent decisions.

1. Converge the server staging model

The server staging tree has three writers with three freshness models (boot rsync of VSIX publics, a 10-skill internal allowlist, four hand-managed locals). 18 of 28 shared skills were stale frozen copies before tonight's merges; the internal library is now the source of truth (four locals homed, PRs #67/#68/#70). Options: extend the allowlist to the full internal set (staging converges automatically; changes live server runtime at next boot), or drop staging internals in favor of the VS Code bundle's resolution. Recommended: extend the allowlist after observing a few nightly cadence receipts.

2. Package-skill roots default mismatch

The resolver's default package-skill root (`/harmoniqs/packages`) doesn't match this fleet's layout (`/armonia/repos/packages`), and no package ships a skills/ dir — the channel is dead wiring. Either fix the default to try both layouts or delete the channel until something uses it. Recommended: add the second path to the default root list (one line, resolver-tested) when the first package-colocated skill lands; until then it's harmless.

3. Legato / Legatissimo naming fate

No Legato.jl exists; circuit compilation is carried by nothing; charter/13 is a two-line stub; yet entitlements.toml grants Legato (default tier) and Legatissimo (issimo tier), and the legato-dev skill is a sharpened stub (kept honest tonight: states plainly no repo exists). Decide: roadmap name to keep (keep stub + entitlements) or drop from entitlements until real. This is a product-naming call — not made autonomously.

Acceptance Criteria

• Each section gets a human decision recorded (comment or close-with-verdict)
• Resulting work, if any, lands as its own issue+PR

Source

Campaign ledger (personal vault, sessions/session-20260826-issimo-skill-freshness.md) §7 + audit casts. Overnight batch, user-delegated 2026-08-26; these three explicitly deferred to daylight.