-----------
 issuepack
-----------

Pack issues into your repo.

```sh
uv tool install .
issuepack new "Fix login redirect" -m "Return to the original page after login."
issuepack ls {search query} --status {open | closed}
issuepack edit 1
issuepack edit 1 --status closed
issuepack edit 1 -m "Append an update to the body."
issuepack help edit
```

Sub-issues are ordinary issues with one parent:

```sh
issuepack new "Improve login"                         # Creates #2
issuepack new "Add redirect tests" --parent 2         # Creates #3
issuepack ls --parent 2                              # Open direct children
issuepack ls --parent 2 --status closed              # Closed direct children
issuepack edit 3 --parent 1                          # Move to another parent
issuepack edit 3 --no-parent                         # Make it a top-level issue
```

`ls` shows each issue's parent in the PARENT column (`-` for top-level
issues). Search and status filters also apply when listing sub-issues.
Sub-issues can have children of their own. Closing a parent or child changes
only that issue's status. Parents must exist, and relationships cannot form
cycles.

Each issue stays in `.issues/<id>.txt`. A child stores `P=<parent ID>` after
the `T=` header, before the blank line and description. Omit `P=` for a
top-level issue. This field can also be changed through `issuepack edit`.