Development record
37-memory.md:84-88 says memory list is the unfiltered list the naming rule forbids; iss-2610171626344967 was resolved by writing that into the brief, so no open record holds the defect, while the same shape for banlist list is open as iss-2609282105240081.
issueopenminoriss-2610252214505831
37-memory.md:84-88 says memory list is the unfiltered list the naming rule forbids; iss-2610171626344967 was resolved by writing that into the brief, so no open record holds the defect, while the same shape for banlist list is open as iss-2609282105240081.
Frontmatter
| id | iss-2610252214505831 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610252214505831-37-memory-md-84-88-says-memory-list-is.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2609282105240081`abcd banlist list` with no flags prints output byte-identical to bare `abcd banlist`, the alias shape the naming chapter (02-constraints/04-naming.md) forbids, and no exception lists it. Found by the v0.11.1 crosscheck (x-115); sub-verb registered at v0.11.0.
- iss-2610171626344967The v0.15.1 release review found the brief at .abcd/development/brief/04-surfaces/37-memory.md:21 out of step with the shipped code. It says: `list` is a shipped sub-verb of /abcd:memory; the naming constraint (.abcd/development/brief/02-constraints/04-naming.md:90-94) forbids a plain unfiltered `<verb> list` at design time, a sub-verb having to do something the bare invocation … In the code: `abcd memory list` takes no flags and no argument ('refuses any argument') and lists every note in both layers unfiltered; neither 37-memory.md nor the bare-invocation enumeration in 04-surfaces/README.md records it as an exception to the rule.