The frontend calls some mounts/files endpoints through raw axios instead of the generated Fern client, and the generated client directory no longer matches a clean regeneration run (files under agenta-api-client/src/generated/ were hand-edited). web/AGENTS.md says JSON mount listings should go through the generated client. On top of that, the download-all export route returns a binary zip but does not declare that response shape in OpenAPI, so a regenerated client method for it would not be usable as-is.
The goal is to get the mount/file calls back onto the generated client with one clean regeneration.
Follow-up from the #5400 backend review; depends on the /files/export rename in #5411/#5412. Cited finding: 2.5 (JSON mount listings should use the generated client per web/AGENTS.md; the generated dir was hand-edited so it no longer matches a regeneration; do the regen after the route rename), plus the binary-response note. Do the regeneration once, after the rename, to avoid churning the generated client twice. The review report is not in the repo, so this summary stands alone.
The frontend calls some mounts/files endpoints through raw axios instead of the generated Fern client, and the generated client directory no longer matches a clean regeneration run (files under
agenta-api-client/src/generated/were hand-edited).web/AGENTS.mdsays JSON mount listings should go through the generated client. On top of that, the download-all export route returns a binary zip but does not declare that response shape in OpenAPI, so a regenerated client method for it would not be usable as-is.The goal is to get the mount/file calls back onto the generated client with one clean regeneration.
POST /files/archiveroute is renamed to/files/export(the rename lands in fix(api): eager archive errors, capped count-only listing, rollup tests #5411/fix(api): relax drive path validation, harden archive, rename export route #5412) so the client matches the shipped route names, replacing the hand-edits.application/zipin OpenAPI so the generated method for it is actually usable.Follow-up from the #5400 backend review; depends on the
/files/exportrename in #5411/#5412. Cited finding: 2.5 (JSON mount listings should use the generated client perweb/AGENTS.md; the generated dir was hand-edited so it no longer matches a regeneration; do the regen after the route rename), plus the binary-response note. Do the regeneration once, after the rename, to avoid churning the generated client twice. The review report is not in the repo, so this summary stands alone.