test(core): update orchestrator-prompt test for cross-platform runtime warning

The orchestrator system prompt was rewritten in 1d8c8f75 to call out both
tmux send-keys (Unix) and the Windows named-pipe write path so the
orchestrator agent doesn't try either. The test still asserted the old
literal "never use raw \`tmux send-keys\`" string. Update it to assert the
new platform-neutral phrasing plus the presence of both runtime mentions.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Priyanshu Choudhary 2026-05-05 01:40:46 +05:30
parent 1d8c8f75ca
commit ffb12e2cdb
1 changed files with 6 additions and 2 deletions

View File

@ -64,7 +64,7 @@ describe("generateOrchestratorPrompt", () => {
expect(prompt).toContain("do not edit repository files or implement fixes");
});
it("mandates ao send and bans raw tmux access", async () => {
it("mandates ao send and bans raw runtime access", async () => {
const generateOrchestratorPrompt = await loadGenerateOrchestratorPrompt();
const prompt = generateOrchestratorPrompt({
config,
@ -73,7 +73,11 @@ describe("generateOrchestratorPrompt", () => {
});
expect(prompt).toContain("Always use `ao send`");
expect(prompt).toContain("never use raw `tmux send-keys`");
// Platform-neutral runtime warning — must call out both tmux (Unix) and the
// Windows named-pipe path so the orchestrator agent doesn't try either.
expect(prompt).toContain("never bypass it by writing to the runtime layer directly");
expect(prompt).toContain("tmux send-keys");
expect(prompt).toContain("named pipe");
expect(prompt).toContain("ao send --no-wait");
});