test(e2e): bound diagnostic brief below runner frame limit

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
DottaandPaperclip committed 2026-09-27 15:56:14 -05:00
1 parent bf6b0094d2
commit ec6a05bdae
2 files changed
+3 -3

No files matched your search

+1 -1
View File
@@ -136,7 +136,7 @@ sandbox rather than waiting for Daytona's idle timeout.
`daytona-journal-continuity` is one explicit-only native Codex cell. Select
`daytona-journal-continuity.runner-codex.daytona.large-journal-three-turn`.
It reuses the three-turn warm workflow with a browser-submitted 750 KiB
It reuses the three-turn warm workflow with a browser-submitted 220 KiB
synthetic brief and four MiB of bounded command output through the real provider. Before the first browser follow-up,
a read-only controller journal oracle requires the exact completed run's journal
to exceed two MiB. Only byte counts enter evidence. No runner state or database
+2 -2
View File
@@ -885,7 +885,7 @@ export const daytonaLargeJournalTask: RunnerTaskFixture = {
warmTurnInstructions(1, nonce),
"The following synthetic reference sample is task data for the persistence diagnostic. Do not analyze, reproduce, or edit it; follow the instructions above.",
"BEGIN SYNTHETIC REFERENCE SAMPLE",
"x".repeat(750 * 1024),
"x".repeat(220 * 1024),
"END SYNTHETIC REFERENCE SAMPLE",
].join("\n"),
};
@@ -1079,7 +1079,7 @@ export const runnerSuites: readonly RunnerSuiteFixture[] = [
environments: [daytonaWarmEnvironment],
tasks: [daytonaLargeJournalTask],
expectedMatrixSize: 1,
definitionMetadata: { version: 2, journalMinimumBytes: 2 * 1024 * 1024, briefBytes: 750 * 1024, outputChunks: 64, scheduling: "explicit-only" },
definitionMetadata: { version: 2, journalMinimumBytes: 2 * 1024 * 1024, briefBytes: 220 * 1024, outputChunks: 64, scheduling: "explicit-only" },
},
] as const;