Retire the Agent File (.af) projection - #93
Conversation
The .af file was a generated projection for a framework this repo does not run: channels, subagents, sandboxes, approval tiers, and hooks have no .af counterpart, so it could not be imported and run anywhere, and Computer was its only reader. Its published copy is preserved in wazootech/data at archives/agent-file/data.af, with the retirement reason recorded there. Removes the generated agents/@wazootech/computer/computer.af (the archived copy lives in wazootech/data), agent/agent-file-declaration.json, the four lib/agent-file-* modules, scripts/export-agent-file.ts, the export/check:agent-file package scripts, and the check:agent-file CI step. No runtime behavior changes: nothing read the file back. Closes the decision in #86.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request removes the Files changed:
|
1 similar comment
|
This pull request removes the Files changed:
|
Closes the decision in #86. Supersedes #87, whose branch was corrupted by the factory: it renumbered every line of
README.md,AGENTS.md, and.github/ARCHITECTURE.md, and reverted #88–#91 (lib/host-secrets.ts, the guild-wide mention policy, and their tests) because it was cut before them.What changed
Removes the
.afprojection and everything that only served it:agents/@wazootech/computer/computer.af(1,798 lines of generated JSON)agent/agent-file-declaration.jsonlib/agent-file-{schema,project,privacy,test}.tsscripts/export-agent-file.tsexport:agent-file/check:agent-filepackage scriptscheck:agent-fileCI step in.github/workflows/verify.ymlNet: 3,367 deletions, 7 insertions.
Why
The projection described less than the agent is — channels, subagents, sandboxes, approval tiers, and hooks have no
.afcounterpart — so it could not be imported and run. Computer does not run a Letta framework, and nothing in the repository read the file back. It was its own only consumer.The published copy is preserved rather than discarded:
wazootech/dataholdsarchives/agent-file/data.afwith the retirement reason recorded at commitfe35e27, so a future consumer can recover the artifact from there.Verification
pnpm typecheck— cleanpnpm test— 174 tests, 21 suites, all passinggrepforagent-file|agentFile|computer.afacross.ts,.tsx,.json,.yml, and.mdreturns only the retirement note inREADME.mdcheck:agent-filestep was a drift guard on a generated artifact.