#963 Rename the harness id to rovo and qualify the frontmatter key - #1199
Merged
Conversation
`--harness rovo` replaces `--harness rovodev` in every command, and the help text and error message list the new value. Re-run `codeassembly install` after upgrading: session-lifecycle hook entries in `~/.rovodev/config.yml` carry the harness id, and stale entries stop relaying events until they are rewritten. Content authors rename the subagent frontmatter overlay `subagents/_data/rovodev.yaml` to `rovo.yaml`. CodeAssembly's name for the harness is now independent of the directory it installs into, which stays `~/.rovodev` until Atlassian's own rename lands.
Skill frontmatter declares `supported-harnesses:` in place of `harnesses:`; content authors rename the key in any skill that narrows itself to specific harnesses. The bare `harnesses:` now belongs to declaration files alone, where it chooses which harnesses a sync run targets.
Guidance, package documentation, and skill reference tables name the `rovo` harness and the `supported-harnesses:` frontmatter key. No reference to `--harness rovodev` or the bare `harnesses:` frontmatter key remains outside the released changelog.
Renames the harness guidance directory to `guidance/_harnesses/rovo/`, completing the rename of the harness id. A content root carrying `guidance/_harnesses/rovodev/` must rename it to `guidance/_harnesses/rovo/`. `codeassembly install` resolves the directory by harness id, and delivers no harness guidance when it finds none there.
Covers two behaviors the harness-vocabulary rename left unguarded: that a skill's `supported-harnesses:` frontmatter key is stripped from the deployed skill, and that every harness receives its guidance file when the full library installs. The guidance check tracks the harness table rather than a fixed list, so a new harness is covered without an edit.
Spells the harness `rovo` in the remaining test fixtures and in the helper that seeds its home directory, leaving `rovodev` in code only where it names Atlassian's own `.rovodev` path.
williamthorsen
added
breaking
Dependency auditProduction dependency audit passed. |
williamthorsen
marked this pull request as ready for review
August 5, 2026 12:41
williamthorsen
added a commit
that referenced
this pull request
Aug 7, 2026
…ssembly-mcp-v0.2.4 codeassembly-v0.6.0 codeassembly-v0.6.0 - #794 feat: Guide kb-add note placement with the store's declared taxonomy (#1223) - #1111 feat: Declare which harnesses sync targets (#1221) - #1214 feat: Allow an artifact to belong to more than one collection (#1219) - #1186 drop!: Dissolve `common-mistakes` into its consumers' guidance (#1217) - deps: Upgrade all deps to latest version - #1203 fix: Bar acceptance-criteria revision prompts to genuine conflicts (#1212) - #1196 feat: Add the .kb/taxonomy.yaml format with drift reporting and back-fill (#1210) - #1165 feat: Make a vetted subset of the library declarable (#1207) - #1197 feat: Report the retired `harnesses:` frontmatter key from `validate` (#1204) - #963 feat!: Rename the harness id to rovo and qualify the frontmatter key (#1199) - #1188 drop!: Retire the bundled Bitbucket inline-comment script (#1198) - #1187 feat: Gate the boolean prefix on a test and add the tail rule it rests on (#1195) factory-v0.2.4 - deps: Upgrade all deps to latest version - deps: Upgrade all deps to latest version - #1209 refactor: Clear factory's remaining lint violations and retire both deferral lists (#1216) - #1208 refactor: Clear the visualizations lint violations and retire six rule deferrals (#1213) kb-v0.4.0 - #794 feat: Guide kb-add note placement with the store's declared taxonomy (#1223) - #1196 feat: Add the .kb/taxonomy.yaml format with drift reporting and back-fill (#1210) codeassembly-lifecycle-v0.3.0 - #963 feat!: Rename the harness id to rovo and qualify the frontmatter key (#1199) codeassembly-mcp-v0.2.4 - #1206 refactor: Retire fleet's lint deferrals (#1211) - #1200 tooling: Retire mcp's lint deferrals and prune the dead root entries (#1205)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Renames the internal ID for the Rovo Dev harness from
rovodevtorovo.--harness rovoreplaces--harness rovodevin every command.Separately, renames the
harnessesfrontmatter key (which narrows a skill to particular harnesses) tosupported-harnesses:to avoid confusion.Why
A forthcoming declaration-file key will also be called
harnesses:, selecting which harnesses a sync run targets rather than narrowing an artifact. Same word, different files, different meaning, and a reader who confuses the two gets no error — only the wrong deployment.Details
🎉 Features
--harness rovoreplaces--harness rovodev. No alias is accepted for the retired value. The--harnesshelp text, its usage line, and the invalid-harness error now derive their accepted-value list from one source, so the next harness reaches all three without an edit.supported-harnesses:in place ofharnesses:. The deploy-time read and thelibrary listdelivery column resolve the key through a single shared constant, and the strip that keeps the key out of a deployed skill is anchored to the qualified name.subagents/_data/rovodev.yamltorovo.yaml, andguidance/_harnesses/rovodev/toguidance/_harnesses/rovo/.harnesses:key fromvalidateis deferred to Report the retiredharnesses:frontmatter key fromvalidate#1197.🧪 Tests
rovo, except whererovodevis the currently used path.📚 Documentation
AGENTS.md, the package README, the partials README, and the content specification namerovoandsupported-harnesses:. The Rovo Dev hook-configuration example carries the new flag value.Closes #963