Loose files under .task/resources/ are invisible to seat accounting #44

New issue

Open

opened 2026-08-02 07:03:24 +00:00 by PerishFire · 0 comments

PerishFire commented

2026-08-02 07:03:24 +00:00

Owner

Environment: concord v0.9.0.

Observed

One task currently holds 80 loose files directly under .task/resources/. resource list reports four seats and none of the files:

$ find .../resources -maxdepth 1 -type f | wc -l
80
$ concord resource list powerformer.net/feat-windows-odeval-node
.../resources/imports
.../resources/odeval-release-4b107dc
.../resources/odeval-release-d668d33
.../resources/odeval-release-e9487cc

resource show refuses them:

$ concord resource show <task> open-design-d3438a57f.bundle
concord: resource seat does not exist: .../resources/open-design-d3438a57f.bundle   # exit 1

Earlier in the same task those loose files totalled 1.29 GiB — six git bundles and two tarballs, the largest 518 MiB. Audit reported memory: WARN 1.3 GiB while the four enumerated seats summed to about 7 MiB.

Consequence

The WARN names a direction but no object. Concord cannot delete bytes inside its own managed tree, so the operator has to du -sh .task/resources/* and rm — which is exactly the raw mutation the skill exists to replace. In this case that meant removing 1.29 GiB by hand, and separately proving the deleted bundles were reconstructible, with no help from Concord at any step.

Proposal

Report N bytes across M entries outside allocated seats as an audit observation, so the WARN resolves to something. Then either let resource remove target an exact unmanaged path under resources/, or offer an explicit adopt-into-seat migration.

Environment: concord v0.9.0. ## Observed One task currently holds 80 loose files directly under `.task/resources/`. `resource list` reports four seats and none of the files: ``` $ find .../resources -maxdepth 1 -type f | wc -l 80 $ concord resource list powerformer.net/feat-windows-odeval-node .../resources/imports .../resources/odeval-release-4b107dc .../resources/odeval-release-d668d33 .../resources/odeval-release-e9487cc ``` `resource show` refuses them: ``` $ concord resource show <task> open-design-d3438a57f.bundle concord: resource seat does not exist: .../resources/open-design-d3438a57f.bundle # exit 1 ``` Earlier in the same task those loose files totalled 1.29 GiB — six git bundles and two tarballs, the largest 518 MiB. Audit reported `memory: WARN 1.3 GiB` while the four enumerated seats summed to about 7 MiB. ## Consequence The WARN names a direction but no object. Concord cannot delete bytes inside its own managed tree, so the operator has to `du -sh .task/resources/*` and `rm` — which is exactly the raw mutation the skill exists to replace. In this case that meant removing 1.29 GiB by hand, and separately proving the deleted bundles were reconstructible, with no help from Concord at any step. ## Proposal Report `N bytes across M entries outside allocated seats` as an audit observation, so the WARN resolves to something. Then either let `resource remove` target an exact unmanaged path under `resources/`, or offer an explicit adopt-into-seat migration.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

PerishFire/concord#44

No description provided.

Rows
Columns