hub-maintenance-workflowlisted

# Hub Maintenance Workflow Use this owner for Harness Hub repository work. ## Workflow 1. Align the maintenance goal and whether it is docs, skill, capability metadata, CLI lifecycle, or source evaluation work. 2. Gather required material: `docs/personal-workflow-distribution.md`, `docs/source-projects.md`, `docs/skill-routing.md`, `capabilities/index.json`, relevant skills, and tests. 3. Write or update spec and acceptance before mutating installable behavior; keep formal artifacts optional for ordinary curation. 4. Write an executable plan with cleanup decisions and validation commands. 5. Clean unneeded files only when ownership is clear; preserve source evidence, upstream skill bodies, and unrelated user edits. 6. Apply narrow changes. 7. Validate with routing tests, `scripts/validate-skills.ps1 -SkipExternal`, and `bun run validate` when TypeScript, tests, capabilities, or CLI behavior changed. 8. Use `effective-interact` for material handoff reports. ## Source And Evaluation Inputs Use repo-local source records and deterministic project files instead of delegating to removed library skills: - `docs/personal-workflow-distribution.md` for the personal distribution rules, TODOs, and acceptance criteria. - `docs/source-projects.md` for upstream URLs, versions, license notes, import decisions, and reference-only candidates. - `docs/harness-vocabulary.md` for local concept boundaries when maintaining Harness Hub-owned skills, reports, or validation language. - `docs/wor