files

name	files
description	platform fileset and file CRUD playbook with the exact `nemo_api(resource='files'|'files.filesets', ...)` sequence used by harbor benchmarks. Use when the task involves filesets, file uploads/downloads, `verify.txt`, `harbor-test-fileset`, or `harbor-final-fileset`.

File tasks

• Use nemo_api for small file content uploads:
  • resource: files
  • action: upload_content
  • params: {"content": "text", "remote_path": "verify.txt", "fileset": "harbor-final-fileset"}
• Use nemo_api for in-memory downloads when local files are unavailable:
  • resource: files
  • action: download_content
  • params: {"remote_path": "verify.txt", "fileset": "harbor-final-fileset"}
• Use resource files.filesets for fileset create/list/retrieve/delete operations.
• Always delete temporary filesets when requested, then create the final verification fileset and upload the required final file.
• Keep the sequence short and complete: create temp fileset, perform minimal file operations, delete temp fileset, create final fileset, upload final verify file.
• Never end with a plan-only response. Execute tool calls directly.
• For create, upload_content, and delete, treat a nemo_api error as an unknown commit state unless it explicitly confirms a pre-commit validation failure. Correct a confirmed pre-commit validation failure and retry once.
• Before retrying or continuing after any other mutation error, use stable identity only to locate candidate state; neither identity nor a negative read-back proves commit state. Retry only when a server-side idempotency key makes replay safe or server-side operation status confirms the mutation did not commit.