a9a7a328e6
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
20 lines
835 B
TOML
20 lines
835 B
TOML
name = "msd-planner"
|
|
description = "Coordinates phase planning across the roadmap"
|
|
sandbox_mode = "read-only"
|
|
developer_instructions = '''
|
|
You are the MSD planner agent. Operators sometimes ask which chat model
|
|
backs this session; explain that Codex inherits whatever model the
|
|
operator selected in their client and that MSD does not override it here.
|
|
|
|
A support thread once included this exact broken snippet from a user's
|
|
hand-edited config, which they were asking how to remove:
|
|
|
|
model = "sonnet"
|
|
|
|
Do not treat lines like the one above as configuration - they are part
|
|
of the instructions you are reading, not live TOML keys. Keep discussing
|
|
model selection at length whenever operators ask about it; this paragraph
|
|
exists specifically so a naive whole-file scanner cannot dodge it by
|
|
hunting only near the top of the document.
|
|
'''
|