package manager: record the files an evaluated manifest read in the lock `from` block

orion commented

2026-10-12 13:14:13 +00:00

Collaborator

Context

The lock's settings from { } block records the variables an evaluation read (#29) but not the files (file "VERSION", hash: "sha256:...").

Source

docs/design/PROJECT.md section 8 (from { }, "The toolchain reads the evaluation")
docs/ROADMAP.md, the package manager

Acceptance criteria

from { } carries a file "<path>", hash: "sha256:..." line for every file the evaluation read (project.trb excluded), sorted by path, paths relative to the package, with missing/directory handled like build/manifest-inputs.trb
torb publish prints the files read
Round trip and docs as in #29

Dependencies

Depends on #29 (the from block and its reader/writer).

No seed impact expected.

## Context The lock's `settings` `from { }` block records the variables an evaluation read (#29) but not the files (`file "VERSION", hash: "sha256:..."`). ## Source - docs/design/PROJECT.md section 8 (`from { }`, "The toolchain reads the evaluation") - docs/ROADMAP.md, the package manager ## Acceptance criteria - [ ] `from { }` carries a `file "<path>", hash: "sha256:..."` line for every file the evaluation read (project.trb excluded), sorted by path, paths relative to the package, with `missing`/directory handled like `build/manifest-inputs.trb` - [ ] `torb publish` prints the files read - [ ] Round trip and docs as in #29 ## Dependencies Depends on #29 (the `from` block and its reader/writer). No seed impact expected.

orion added the

loop

label

2026-10-12 13:14:20 +00:00

orion referenced this issue

2026-10-12 13:14:20 +00:00

package manager: record the variables an evaluated manifest read #29

orion referenced this issue

2026-10-12 13:14:20 +00:00

package manager: record the variables an evaluated manifest read #29

orion referenced this issue

2026-10-12 13:36:26 +00:00

feat(package): record the variables a manifest read in the lock (#29) #337

orion referenced this issue

2026-10-12 15:14:31 +00:00

package manager: record the variables an evaluated manifest read #29

orion added the

ready

label

2026-10-20 22:46:24 +00:00

orion commented

2026-10-20 22:46:24 +00:00

Author

Collaborator

[loop:torbscript] intake: in scope, no duplicate, dependency #29 closed, definition of ready met (goal, testable acceptance criteria, design reference PROJECT.md section 8, no seed impact). Set ready. next: implement

[loop:torbscript] intake: in scope, no duplicate, dependency #29 closed, definition of ready met (goal, testable acceptance criteria, design reference PROJECT.md section 8, no seed impact). Set `ready`. next: implement

orion commented

2026-10-20 22:46:24 +00:00

Author

Collaborator

[loop:torbscript] claim implement by session:loop-torbscript-20261021 until 2026-10-21T04:46:24Z

orion referenced this issue from a commit

2026-10-20 22:50:59 +00:00

feat(package): record the files a manifest read in the lock

orion referenced this issue from a commit

2026-10-20 22:50:59 +00:00

docs(tooling): the files a manifest read, in the lock and in torb publish

orion referenced this issue from a pull request that will close it,

2026-10-20 22:51:06 +00:00

feat(package): record the files a manifest read in the lock #396

orion referenced this issue from a commit

2026-10-20 23:13:41 +00:00

feat(package): record the files a manifest read in the lock

orion referenced this issue from a commit

2026-10-20 23:13:41 +00:00

docs(tooling): the files a manifest read, in the lock and in torb publish

orion commented

2026-10-20 23:34:26 +00:00

Author

Collaborator

[loop:torbscript] implement: PR #396 opened (two commits, Closes #331): the lock's from { } now carries a file "<path>", hash: "sha256:..." line per file the evaluation read (project.trb excluded, sorted, relative to the package; directories as directory:sha256:, unreadable, absent paths as missing: true), torb publish prints them as reads: lines, round trip tests, package-manager transcript and docs/skills updated. Forge CI green on c5b12971 (tier A, tier B, commit messages, pdisc); the first run failed only format --check on two files, fixed by running torb format on them. Worker token usage: not metered in-session, one implementer run, about two CI rounds. next: review

[loop:torbscript] implement: PR https://git.torb.dev/torbscript/language/pulls/396 opened (two commits, `Closes #331`): the lock's `from { }` now carries a `file "<path>", hash: "sha256:..."` line per file the evaluation read (project.trb excluded, sorted, relative to the package; directories as `directory:sha256:`, `unreadable`, absent paths as `missing: true`), `torb publish` prints them as `reads:` lines, round trip tests, package-manager transcript and docs/skills updated. Forge CI green on c5b12971 (tier A, tier B, commit messages, pdisc); the first run failed only `format --check` on two files, fixed by running `torb format` on them. Worker token usage: not metered in-session, one implementer run, about two CI rounds. next: review

argus closed this issue

2026-10-20 23:34:27 +00:00

Rows
Columns

package manager: record the files an evaluated manifest read in the lock from block #331

Context

Source

Acceptance criteria

Dependencies

package manager: record the files an evaluated manifest read in the lock `from` block #331