golem15/msd-core
3
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

refactor: remove dead descriptor-driven mechanisms (no remaining consumer)

Browse Source 
Drop code whose only consumer was a retired runtime: hostBehaviors readers for
agentFileExtension, localTargetIsProjectRoot, sharedHooksDirName,
skillsManifestPrefix and skipCodexSkillsManifest; the empty
NON_REGISTRY_CONFIG_HOME_DESCRIPTORS array and live-config-guard plumbing; the
empty RUNTIME_NOTE_AUDIENCE_BY_HEADING filter; the unused resolveVersionFrom
export; and the WINDSURF_SESSION_ID workstream session key. Delete tests that
only exercised those mechanisms.
This commit is contained in:
Jakub Zych
2026-10-06 20:49:35 +02:00
parent fe3ed06691
commit 6b0b92674a
25 changed files with 63 additions and 912 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/CONTEXT-INDEX.json
View File

@@ -49,7 +49,7 @@
{
"id": "CONFIG.LOCATION.SEAM.scrub-set",
"klass": "CONFIG",
"value": "tests/helpers.cjs CONFIG_LOCATION_ENV_KEYS is DERIVED from five sources rather than maintained as one hand-written list (source 4 IS a literal residue list, for vars that fit no other rung — what is never hand-listed is the SET): capability-registry runtimes[].runtime.configHome.env AND [].configHome.skillsHome.env + runtime-homes NON_REGISTRY_CONFIG_HOME_DESCRIPTORS[].env AND [].skillsHome.env (a descriptor is a descriptor — BOTH descriptor rungs walk skillsHome, which resolves independently via resolveSkillsBaseFromDescriptor) + runtime-homes MSD_LOCATION_ENV_KEYS + a residue list (GROK_AGENTS_HOME, MSD_RUNTIME, MSD_PROJECT, MSD_WORKSTREAM) + WRITE_ESCAPE_PERMISSION_ENV_KEYS (MSD_ALLOW_SYMLINKED_DEST — a permission, not a location: it names no path but disarms the symlink-escape guard, so blanking it makes the guard STRICTER, never looser); adding a config-location var means making it ENUMERABLE at one of those sources, not appending a literal"
"value": "tests/helpers.cjs CONFIG_LOCATION_ENV_KEYS is DERIVED from four sources rather than maintained as one hand-written list (source 3 IS a literal residue list, for vars that fit no other rung — what is never hand-listed is the SET): capability-registry runtimes[].runtime.configHome.env AND [].configHome.skillsHome.env (skillsHome resolves independently via resolveSkillsBaseFromDescriptor, so both are walked) + runtime-homes MSD_LOCATION_ENV_KEYS + a residue list (GROK_AGENTS_HOME, MSD_RUNTIME, MSD_PROJECT, MSD_WORKSTREAM) + WRITE_ESCAPE_PERMISSION_ENV_KEYS (MSD_ALLOW_SYMLINKED_DEST — a permission, not a location: it names no path but disarms the symlink-escape guard, so blanking it makes the guard STRICTER, never looser); adding a config-location var means making it ENUMERABLE at one of those sources, not appending a literal"
},
{
"id": "CONFIG.LOCATION.SEAM.two-families",
@@ -119,7 +119,7 @@
{
"id": "LIVE-CONFIG.GUARD.SEAM.non-root-targets",
"klass": "LIVE-CONFIG",
"value": "resolveExtraWatchTargets covers THREE live write surfaces that are not runtime config ROOTS (skills bases are a DELIBERATE non-target — the config-root layout misfires beneath them, so they need their own layout): $MSD_HOME/.msd watched WHOLESALE (exclusively MSD-owned, so the shared-root trap does not apply) plus ONE config.toml per NON_REGISTRY_CONFIG_HOME_DESCRIPTORS entry, each watched as a SINGLE FILE (those roots belong to their products); the targets are DERIVED by iterating that array, never by calling a named resolver, so a further descriptor is picked up without editing the guard PROVIDED it owns the same NON_REGISTRY_OWNED_FILE ('config.toml') — one that owns a different filename needs a per-descriptor mapping, the named residual the guard states at its own definition. SECOND RESIDUAL: config.toml is not all MSD writes into those roots — installSharedHooksBundle also populates <root>/hooks/, which is UNWATCHED; closing it is a layout decision, like skills bases; passed to snapshotLiveConfig explicitly so a fixture-root caller cannot pull the real ~/.msd into its snapshot"
"value": "resolveExtraWatchTargets covers the live write surface that is not a runtime config ROOT (skills bases are a DELIBERATE non-target — the config-root layout misfires beneath them, so they need their own layout): $MSD_HOME/.msd watched WHOLESALE (exclusively MSD-owned, so the shared-root trap does not apply); passed to snapshotLiveConfig explicitly so a fixture-root caller cannot pull the real ~/.msd into its snapshot"
},
{
"id": "LIVE-CONFIG.GUARD.SEAM.scope",