CLAUDE.md: the mistyped label separator errors now, it does not pass
This warned that `--label area:ops` "matches nothing and silently returns unfiltered results". That stopped being true when hive-forge learned to suggest the nearest name: it now exits non-zero with `unresolved label name(s): area:ops (did you mean "area/ops"?)` and lists the available labels. Measured, not assumed — the old text is what sent me looking for a silent failure that no longer exists, which is the specific cost of a doc that describes a fixed bug.
This commit is contained in:
parent
196805bfc0
commit
ff7897f9bc
1 changed files with 2 additions and 3 deletions
|
|
@ -11,9 +11,8 @@ when you need depth on a subsystem. This file is the index.
|
|||
the forge, so a hardcoded loopback address fails to connect.
|
||||
- Operator/agent trust-boundary design:
|
||||
**[docs/boundary.md](docs/boundary.md)** (`area/ops` issues
|
||||
for the deployment/gateway/privsep work — the separator is a **slash**;
|
||||
`--label area:ops` matches nothing and silently returns *unfiltered*
|
||||
results, which reads like a backlog rather than like an error).
|
||||
for the deployment/gateway/privsep work — the separator is a **slash**,
|
||||
and `--label area:ops` now fails with `did you mean "area/ops"?`).
|
||||
- Agent trust model (trust boundary, prompt-injection threat model,
|
||||
capability = accepted risk), credential isolation + sandbox threat model:
|
||||
**[docs/security.md](docs/security.md)**.
|
||||
|
|
|
|||
Loading…
Reference in a new issue