File item 471: ship jira-rest as a claude-config tool
CI / tests (pull_request) Successful in 2m49s

This commit was merged in pull request #662.
This commit is contained in:
Lilleman
2026-11-20 12:26:13 +01:00
parent df224cc82a
commit a84c39d798
+13 -1
View File
@@ -6,7 +6,7 @@
`Bar = 0.1`
`Next ID = 471`
`Next ID = 472`
## Items
@@ -31,6 +31,7 @@
| 264 | 0.16.0 | | | **Report the comprehension seats and the escalated subagents as subagent types of their own in `routing-figures.md`, with their dollars.** | 2 | 2 | 1 | 3 | 3 | 1.4 by 5 | 1.7 |
| 323 | 0.16.0 | | | **Count a release review as landed once its pull request has merged, whatever its commits are titled.** | 3 | 2 | 3 | 6 | 3 | 1.4 by 3, 1.5 by 2 | 1.7 |
| 342 | 0.16.0 | | | **Research the tooling agents read, search and run commands with once more, and file an item for each tool that cuts tokens a replay shows keep quality.** | 1 | 2 | 1 | 2 | 3 | 1.4 by 3, 1.5 by 2 | 1.7 |
| 471 | 0.16.0 | | | **Ship `jira-rest METHOD PATH [BODY]`, which makes one Jira Cloud REST call with the credentials of the project's config, or do-epic's, reading the env file itself, so an agent calls Jira without naming a file rule-hook guards.** | 2 | 2 | 4 | 6 | 3 | 1.6 by 3, 1.4 by 2 | 1.7 |
| 149 | 0.16.0 | | decision | **Fill each release by priority up to a capacity it states, in place of the bar, and move what does not fit to a later release.** | 4 | 2 | 3 | 7 | 5 | 1.1 by 7 | 1.6 |
| 165 | 0.16.0 | | | **Make this repo's tests assert the facts a prompt or help text carries in place of its sentences, and drop the tests that scan source or assert a constant.** | 3 | 2 | 1 | 4 | 5 | 1.1 by 4, 1.4 by 3 | 1.6 |
| 392 | 0.16.0 | | owner | **Group bin/'s packages by concern into seven folders (plan, records, integrations, loop, review, forge and host), so a newcomer finds a tool's neighbours in one place.** | 3 | 1 | 3 | 5 | 7 | code health by 4 | 1.6 |
@@ -313,6 +314,17 @@ Dropped in 312's round, and why; look again only where the reason has changed:
- LSP, repo maps and outline scripts: item 231's trial lost findings and agents didn't call them; the only figures found since are a vendor's and a blog's.
- Compact test reporters and output filters such as rtk: this archive's test output is a few thousand tokens per release, and the filters' figures are their own; trimming read output is item 311's ceiling.
### 471. Ship `jira-rest METHOD PATH [BODY]`, which makes one Jira Cloud REST call with the credentials of the project's config, or do-epic's, reading the env file itself, so an agent calls Jira without naming a file rule-hook guards.
Once a Jira credentials file is a config's `env-file`, rule-hook's `env-file-read` refuses every Bash command that names it. A machine's own rules that tell agents to `source` it and `curl` Jira then stop working. On 2026-11-20 this happened on a machine whose rules call Jira that way, and a machine-only script, `~/.local/bin/jira-rest`, took their place. The human asked for it as a claude-config tool, so every machine has it.
- `jira-rest METHOD PATH [BODY.json | -]` sends one call to a path under `/rest/`, with the body from the file or stdin, and prints Jira's JSON answer, or `null` for an empty one. A refused call exits non-zero with the message `atlassian.client.jira_errors` gives. No output, error or log line holds a credential.
- The site and the env file come from the project's config where the checkout has one whose `plan` or `goals-and-audience` is a Jira epic: the epic's site and the config's `env-file`. Otherwise they come from do-epic's config: `jira-url` and `env-file`. Where neither holds them, it fails, naming both places.
- It sends through `atlassian.client`, as `plan_store` and `do_epic` do, so it gains their error messages and timeouts.
- `--help` states the contract, and README → `## Tools` lists the tool.
After it ships, the machine's `~/.local/bin/jira-rest` is removed, and its rules call the shipped tool.
### 149. Fill each release by priority up to a capacity it states, in place of the bar, and move what does not fit to a later release.
A release's capacity is a sum of its items' cost, as the formula counts it. Each project states its own; the human sets the first value per project. Nothing is deleted by score.