Make OpenCode authoring responsive and expand the managed skill references. Add conflict-aware import/export, real-provider reference workflows, and tracked V2 generation for reliable budget accounting.
987 B
Pipelines maintenance
When changing user-facing behavior or learning a confirmed runtime limitation,
update the relevant packaged OpenCode skill reference in
internal/author/skill/references/ in the same change. Keep SKILL.md a concise,
task-directed index: preserve ask-first authoring and never preload every reference.
Separate current capabilities, dated verification evidence, deployment state and
unimplemented ideas. Do not turn mocked or structural checks into live claims.
For new references, update internal/author/install.go's managed file inventory.
Run the author package tests: they check embedding, reference links, installation,
upgrades and protection of user modifications. Never hand-edit an installed copy
as the source of truth; refresh it with the current-source pipelines skill install
only when installation is requested. Do not deploy runtime changes merely because
the skill is updated. Keep README/topic docs and the packaged reference consistent.