docs: refresh data.af after correcting Computer's role

[EthanThatOneKid]

Summary

Computer is Wazoo's general assistant for the whole team, with engineering as one domain it runs as a pipeline, not its whole identity. That correction landed in wazootech/computer (PR wazootech/computer#75) across the root instructions, the allowlisted persona and scope blocks, the architecture doc, and the README.

This PR propagates it to the two places in this repository that restated the old framing:

• agents/@wazootech/data/data.af regenerated from the corrected source in wazootech/computer (scripts/export-agent-file.ts). The generated system block and the scope block now read "Computer is the team's general assistant, and it owns the engineering pipeline".
• README.md no longer calls wazootech/computer "the delivery-pipeline agent" in the repo relationship section.

Verification

The file is a generated projection, not hand-written. Re-exported from wazootech/computer at PR #75 head with pnpm run export:data-agent-file, then confirmed byte-stable with pnpm run check:data-agent-file. Computer's verify workflow passes with these contents committed on both sides.

Note

agents/@wazootech/data/README.md describes data.af as generated by scripts/export-agent-file.ts in wazootech/computer, which is where the source and the export tooling live. The copy here is a published mirror.

[wazoocomputer]

I hit an error while handling your request (Model provider API error: Authentication Fails, Your api key: ****53a6 is invalid).

Please try again, rephrase, or reach out if it keeps failing.

Error id: 1952dd7a-696a-4042-8f25-0fd762afa0c9

[wazoocomputer]

This session could not recover from an error (Model provider API error: Authentication Fails, Your api key: ****53a6 is invalid).

Start a new comment to continue.

Error id: 1952dd7a-696a-4042-8f25-0fd762afa0c9

[EthanThatOneKid]

Change request — hold until wazootech/computer#75 lands, and this repo has no CI to catch drift

The content is correct. I verified the part that matters most for a generated file, which is that the mirror actually matches its generator:

• agents/@wazootech/data/data.af here is byte-identical to agents/@wazootech/data/data.af on wazootech/computer#75 — I extracted the embedded system string from both and diffed them, then regenerated from the source with the exporter and compared again. Same bytes.
• The embedded system and scope blocks do carry the corrected framing ("Computer is the team's general assistant and owns the engineering pipeline"), and the README.md wording change is consistent with the rest of the repository.

Why it should still wait. This file is a projection of source that lives in wazootech/computer, and that source only says "general assistant" once #75 lands. Merging this first would leave the published mirror one PR ahead of the thing it is generated from — and #75 is not currently mergeable: it needs a rebase after #67, and its own new CI gate (pnpm run check:agent-file) fails against any tree where another open PR has edited agent/instructions.ts or added a tool, so it has to land last and regenerate computer.af. Land this after #75, then re-export and confirm byte-stability rather than reusing this diff.

Separately: this repository has no CI. There is no .github/ directory, so data.af drift cannot be caught here — which is exactly the class of change this PR is. The check that would catch it already exists next door (pnpm run check:data-agent-file in wazootech/computer, which regenerates from agents/data/agent and fails on any diff). Worth adding a small check workflow to this repo that pins the upstream revision, clones wazootech/computer at it, runs the exporter in --check mode against this file, and fails on a diff. Otherwise the mirror stays verified only by whoever remembered to look.