Skip to content

[Chore] Add workflow regression coverage - #1144

Draft
roomote-roomote[bot] wants to merge 1 commit into
developfrom
feature/workflow-regression-coverage-1bhpatn104jqe
Draft

[Chore] Add workflow regression coverage#1144
roomote-roomote[bot] wants to merge 1 commit into
developfrom
feature/workflow-regression-coverage-1bhpatn104jqe

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

Opened on behalf of Matt Rubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

  • Strengthened the stable Roomote identity contract while removing assertions tied to obsolete harness-specific guidance.
  • Added explicit regression coverage for the three required first-hop workflows.
  • Added coverage that the default Autonomous path remains incomplete until every changed repository has a confirmed draft pull request.

Why this change was made

The global identity prompt was recently narrowed to identity and personality while workflow policy moved to dedicated runtime layers. These tests protect the intended split and catch routing or delivery regressions without restoring duplicated prompt behavior.

Impact

There is no runtime behavior change. Future prompt and workflow edits will fail focused tests if they drop Roomote identity, bypass required workflow routing, or stop before confirmed draft PR delivery.

@roomote-community

roomote-community Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

1 issue outstanding. See task

  • Assert the initial-routing contract rejects a fourth first-hop workflow. (packages/cloud-agents/src/server/workflows/__tests__/standardTaskExplicitInvocationRouting.test.ts:66)

Reviewed d3a108a

'`explain-repo-code` for understanding, explanation, and code-reading questions',
);
expect(harnessInstructions).toContain(
'Unless the request begins with an explicit skill invocation, always start with one of `implement-changes`, `plan-repo-implementation`, or `explain-repo-code`.',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This only checks that the three existing workflow names remain present. It still passes if a fourth initial-routing option is added, even though the contract requires exactly these three. Please assert the initial-routing menu/cardinality (or otherwise reject additional first-hop workflows) so this regression test protects the stated invariant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant