SR-11 M2 — drop legacy skill table + skill_overrides_json column + dead resolver code #879
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks#879
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
User story
As a platform engineer, I want the legacy
skilltable, theagent_type.skill_overrides_jsoncolumn, and the resolver code paths that read them dropped, so that the codebase has no dead branches and the schema reflects the actual model.Land this PR no earlier than one full release after SR-4 ships, so that any rollback can still consult the legacy data.
Acceptance criteria
Schema
skill(the four-scope ladder table).agent_type.skill_overrides_json.Code
apps/server/src/infrastructure/database/schema/agent-config-scope.ts'sskillschema export. Other kinds (systemPrompt,pluginBinding,mcpServer,pluginMarketplace) stay.agent-type-config.tsif SR-4 left any behind (it should have removedresolveSkill, but verify).loadSkillcache (skillCacheMap) and theloadSkillexport — by this point the only consumer is the SR-6 library endpoint, which can read directly from disk.STATELESS_SKILLSconstant if SR-4 left it.Verification
just qapasses.Out of scope
agent_type_configaggregate as a whole — only the skill-relevant pieces.References
specs/skills-rework.md§M2 — drop legacy tables/columns.apps/server/src/infrastructure/database/schema/agent-config-scope.ts,apps/server/src/infrastructure/database/agent-type-config.ts.