Repository navigation
Tags
Tags
chore: prepare Studio 0.7.37 with localized changelog (EKKOLearnAI#3445)
fix(tos): align package assets with registered dotted application ID
fix(tos): fit desktop icon within platform SVG validation limits
feat(tos): add opt-in platform parsing test to isolated workflow
[codex] complete Windows drive-root workspace handling without trimmi… …ng file paths (EKKOLearnAI#3396) * fix(workspace): accept a Windows drive root as the workspace Setting a session workspace to a Windows drive root (`D:` or `D:\`) made every Agent run fail before it started with `EPERM: operation not permitted, mkdir 'D:'`. Windows reports access denied, not "already exists", for a path it cannot create, and Node only swallows EEXIST/ENOTDIR while walking a recursive mkdir — so a directory that always exists could not be ensured. - `ensureDirectory` accepts a drive root as-is, and treats a permission error over a directory that does exist as success. - A bare drive letter is canonicalized to `D:\`. It is drive-relative on Windows, so it used to resolve against the process's cwd on that drive. - `write_file` gets the same treatment: the parent of `D:\notes.txt` is the drive root itself. Verified with unit tests (EPERM replayed against a mocked mkdir) and against a real server: with the workspace set to `D:` and to `D:\` the run now reaches run.started with no EPERM, where the previous build returned `EPERM: operation not permitted, mkdir 'D:\'` and never started the run. * docs(ekko-agent): refresh the generated public API inventory `api:docs:check` compares every exported declaration under `src/` against the generated block in docs/API.md, so the new `src/tools/directory.ts` exports made the Build workflow stop at "Check repository harness". Regenerated with `npm run api:docs:update`; `npm run harness:check` passes again. * fix: preserve file paths and prepare remote drive-root workspaces * fix: authorize canonical remote drive-root workspaces * fix: prepare remote file parents at Windows drive roots --------- Co-authored-by: misakano7545 <misakano7545@protonmail.com> Co-authored-by: Lux <wangw9475@agent.qq.com>
PreviousNext