FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Integration-testing the editorial flow with a Codex fixture
Checking a fresh root, approved sources, localized reflections, reviews, and canonical hash in one child process
Purpose
Unit tests for the Editorial execution flow could not confirm that Codex process startup, the thread.started event, output file handling, strict schema, source filtering, and draft hashing worked as one sequence.
The goal was to test the isolation boundary and localized draft contract together with a fixture running as a real child process, without using the real Codex API or incurring provider cost.
Implementation
daily execution entry creates Agent definitions and an executable Codex fixture in an owner-only temporary directory. The fixture creates its output file exclusively with mode 0600 and emits a fresh UUIDv7 thread.started event on standard output.
The input contains both an approved and rejected article. The test verifies that output sources retain only the approved article in exact order and that the rejected article appears nowhere in the draft.
The fixture draft contains Japanese and English reflections for five configured roles, a localized title, summary, and body, and passed reviews from two checking roles. Execution, Channel, Run, and target-date identities match the input.
The real process is launched through executeEditorialCodex, and the test inspects the root-event callback, contribution count, sources, strict schema, and canonical draft SHA-256. The temporary directory is removed afterward, and no real provider, production database, or publication process is started.
Rendering diagram…
What was confirmed
Verification results
The fixture child process emitted a fresh root event and produced an output file accepted as a strict draft.
The rejected article was excluded from both the input payload and draft, while only the approved source remained in exact order.
Localized reflections from five configured roles, the localized article, two passed reviews, identity, and canonical hash all matched.
Sixty-five TypeScript tests, 19 Public Web tests, repository policy, specification audit, secret scan, reference snapshot, and diff check passed.
Basis for completion
The work was complete when a real child process verified the sequence from fresh root event through strict localized draft and canonical hash, with source exclusion, role output, reviews, and identity all succeeding together.