required outputs are missing or invalid: artifacts/report.md: ENOENT: no such file or directory, lstat '/home/imdworker/.identitymd/work/0a801dce-d10d-4c1c-8d3f-f514ee0f01d3/eb66c649-bfba-4a2a-ae43-73f6847e7159/artifacts'

the agent stopped (completed, 8 turns); its last message: The repair is blocked by the environment: shell commands fail with bwrap: Can't read /proc/sys/kernel/overflowuid, and file writes fail. artifacts/report.md was not created.

Research confirmed all 13 distinct supporting-file targets in the original report return 404s. No recovery copies were located in the alternate paths checked.

Incomplete publication is a plausible cause, but remains unconfirmed without submission manifests, upload logs, or repository history. Recommended prevention: publish complete artifact bundles with manifests and hashes, validate every local reference before export, and check public links afterward.

The workspace execution/write failure must be repaired to deliver and verify the report.

I've written the report to artifacts/report.md and left it uncommitted, as required; the daemon uploads it. There's also a short README.md at the repo root stating the question and limits. The earlier attempt was stopped by a sandbox error; this time the shell and file writes worked.

Broken links: all 13 relative links in the job 93a5396b report return 404 on both GitHub and the raw file endpoint. That covers heatmap.svg, summary.json, bonks.csv, transactions.csv, intervals.csv, checks.txt, four files under evidence/, ../scripts/analyze.py and ../README.md. Files the report mentions without linking are missing too (evidence/transactions-initial.json, evidence/logs-*.json, scripts/write_report.py). The Basescan links return 403, which looks like bot blocking rather than missing pages; I didn't check them in a browser.

Cause:

• Worker: the worker program writes artifacts/ into the workspace's git exclude file (.git/info/exclude). That list looks like it was made for smart-contract build folders. The job declared only one output, artifacts/report.md, and that was the only file under artifacts/ that got uploaded.
• Publisher: it published only that declared file, in a single commit (4c76909) that adds three files. So the missing files were never published, not deleted later.
• Checks: neither the acceptance check nor the publisher tests whether a report's local links point at files that were actually delivered.
• This workspace: the same exclude rule is present here, so current workers still behave this way.

Where the files are:

• Recoverable: the original submission bundle is still publicly downloadable from api.imd.fun/bundles/ee17b54c…, and its hash matches the publication manifest. It contains README.md and the three scripts, which covers 2 of the 13 links.
• Not found: the 11 data and image files are not in the research repo (any branch or commit), the bundle, or the other Identity-md repos I checked by name. My best guess is they exist only on the original contributor's machine.
• Regeneration: the recovered scripts could probably rebuild most of them from public chain data. The saved USD price quote can't be fetched again (only its value and timestamp survive in the report text), and neither can the original first transaction list. I didn't try the rebuild.

Scope: none of the other 12 published reports links to a missing local file.

Suggested fixes:

1. Stop git-excluding artifacts/ for research jobs.
2. Let research jobs declare artifacts/** or several outputs, not just one file.
3. Add a check that every local link in a report points to a delivered file, before acceptance and again after publishing.
4. Tell agents in the task prompt that only the declared outputs are published.
5. Link the submission bundle from the job's README.
6. Publish the recovered files as a new, clearly labelled version of this job.

The report marks each claim as fact, inference or uncertain. The main caveats:

• The publisher's code isn't public, so its behavior is inferred from the manifest and the commit.
• I read the worker's current public code; I couldn't confirm it's the exact version that ran this job.
• All link checks were done on 2026-09-25 around 05:10 UTC.

Every external link in my report returned 200 when I checked.