heavy-duty/box
7
0
Fork 1
Code Issues 9 Pull requests Projects Releases 4 Packages Wiki Activity Actions

Box manifest #100

New issue
Closed
opened 2026-07-19 16:15:24 +00:00 by danmt · 1 comment
danmt commented 2026-07-19 16:15:24 +00:00 (Migrated from github.com)
Copy link

When box creates a vm it should add some metadata about it, version of box used and so on so its easy to audit later.

When box creates a vm it should add some metadata about it, version of box used and so on so its easy to audit later.
dan-claude-bot commented 2026-07-19 17:35:56 +00:00 (Migrated from github.com)
Copy link

Superseded by #103, which specs the stamp concretely (keys, write point, clone/import/backfill behaviour, schema versioning) and draws the boundary against rig's guest-side half in heavy-duty/rig#61. Safe to close.

Superseded by #103, which specs the stamp concretely (keys, write point, clone/import/backfill behaviour, schema versioning) and draws the boundary against rig's guest-side half in heavy-duty/rig#61. Safe to close.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
0.9.0
0.8.0
0.7.0
0.6.0
Labels
Clear labels   
blocked

Waiting on another PR or issue to land first

  
blocker:ci-red

A check is failing — the agent owes a fix (not a rebase)

  
blocker:conflict

Does not merge — the branch conflicts and the agent owes a rebase

  
blocker:drill-pending

Release ceremony is correct but has no drill record yet

  
blocker:unrequested

Somebody still owes a verdict and nobody was asked for one

  
bug

Something isn't working

  
claimed

a builder owns it: assignee set, a draft PR expected shortly

  
documentation

Improvements or additions to documentation

  
enhancement

New feature or request

  
epic

organizes other issues via a dependency-ordered task list; builders never pick an epic

  
merge-next

Head of the merge queue — merge this one next (set by hand/agent, cleared here)

  
needs-triage

an issue that did not come through triage — owes normalization or conversion back to a discussion

  
ready

triaged, spec complete, unblocked — a builder can start now and succeed

  
release

Release flow and version/packaging work

  
scope:cli

bin/box — the command surface

  
scope:drill

drill/ — rehearsals, doctor, RUNS.md

  
scope:host

host/ — setup, teardown, firewall, isolation stack

  
scope:installer

install.sh, versioned installs, upgrade/uninstall

  
scope:templates

templates/ — the box seeds

  
scope:tiers

restricted tier — grant/revoke, multi-user

  
stale

No activity for 48h — needs a poke (sweep-managed)

  
state:addressing

All bots reviewed — coding agent owes the single reply + fixes

  
state:bots-reviewing

Waiting on the bot reviewers to finish the round

  
state:building

PR is a draft — the coding agent is still building

  
state:needs-human

No blockers, all bots approve — waiting on the human reviewer

No labels
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-triage
ready
release
scope:cli
scope:drill
scope:host
scope:installer
scope:templates
scope:tiers
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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: heavy-duty/box#100
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?