@memnexus-ai/mx-agent-cli 0.1.296-next.3 → 0.1.296-next.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (44) hide show
  1. package/dist/__tests__/coordination-401-production-wiring.test.js +67 -1
  2. package/dist/__tests__/coordination-401-production-wiring.test.js.map +1 -1
  3. package/dist/__tests__/coordination-brief.test.js +58 -1
  4. package/dist/__tests__/coordination-brief.test.js.map +1 -1
  5. package/dist/__tests__/coordination-client.test.js +113 -1
  6. package/dist/__tests__/coordination-client.test.js.map +1 -1
  7. package/dist/__tests__/coordination-command.test.js +288 -2
  8. package/dist/__tests__/coordination-command.test.js.map +1 -1
  9. package/dist/__tests__/provision-completion-rows.test.js +329 -64
  10. package/dist/__tests__/provision-completion-rows.test.js.map +1 -1
  11. package/dist/__tests__/provision-resume.test.js +146 -0
  12. package/dist/__tests__/provision-resume.test.js.map +1 -1
  13. package/dist/__tests__/provision-row12-stub-server.test.d.ts +21 -0
  14. package/dist/__tests__/provision-row12-stub-server.test.d.ts.map +1 -0
  15. package/dist/__tests__/provision-row12-stub-server.test.js +262 -0
  16. package/dist/__tests__/provision-row12-stub-server.test.js.map +1 -0
  17. package/dist/__tests__/team-token-probe.test.d.ts +16 -0
  18. package/dist/__tests__/team-token-probe.test.d.ts.map +1 -0
  19. package/dist/__tests__/team-token-probe.test.js +295 -0
  20. package/dist/__tests__/team-token-probe.test.js.map +1 -0
  21. package/dist/commands/coordination.d.ts.map +1 -1
  22. package/dist/commands/coordination.js +48 -5
  23. package/dist/commands/coordination.js.map +1 -1
  24. package/dist/commands/create.d.ts +28 -10
  25. package/dist/commands/create.d.ts.map +1 -1
  26. package/dist/commands/create.js +123 -33
  27. package/dist/commands/create.js.map +1 -1
  28. package/dist/lib/coordination-client.d.ts +11 -0
  29. package/dist/lib/coordination-client.d.ts.map +1 -1
  30. package/dist/lib/coordination-client.js +79 -18
  31. package/dist/lib/coordination-client.js.map +1 -1
  32. package/dist/lib/coordination-token.d.ts +20 -0
  33. package/dist/lib/coordination-token.d.ts.map +1 -1
  34. package/dist/lib/coordination-token.js +1 -1
  35. package/dist/lib/coordination-token.js.map +1 -1
  36. package/dist/lib/team-token-probe.d.ts +120 -0
  37. package/dist/lib/team-token-probe.d.ts.map +1 -0
  38. package/dist/lib/team-token-probe.js +202 -0
  39. package/dist/lib/team-token-probe.js.map +1 -0
  40. package/dist/lib/templates.d.ts +1 -1
  41. package/dist/lib/templates.d.ts.map +1 -1
  42. package/dist/lib/templates.js +1 -1
  43. package/dist/standards/known-issues-standard.md +380 -0
  44. package/package.json +1 -1
@@ -0,0 +1,380 @@
1
+ # Known-issues standard
2
+
3
+ Where a team's known-issues backlog lives.
4
+
5
+ Citations in this file resolved against `origin/main` at `471dad1`, 2026-09-22, and were
6
+ re-derived against that tree. Most code citations state `file:line`. Two name a file and a grep
7
+ instead, where the lines move often enough that a number would be wrong within a month.
8
+
9
+ The counts in this file move as teams file. Each one states its command and its date. Re-run the
10
+ command rather than quoting the number.
11
+
12
+ ## How this standard reaches you
13
+
14
+ This file is not injected into agent context, and two things stop it. It is not in the four-file
15
+ allowlist at `mx-agent-system/cli/src/lib/standards.ts:47-51`. It also holds no
16
+ `<!-- behavioral-start -->` marker, so `readStandardBlock` at `standards.ts:148-155` would refuse
17
+ it even if it were listed. Its content would not fit either: the four injected blocks total
18
+ 14,765 bytes against the 16,384-byte ceiling at `standards.ts:55`, and `standards.ts:201-215`
19
+ returns an empty block rather than a truncated one.
20
+
21
+ Teams receive this standard through the product team's coordination directive of 2026-09-22 and
22
+ through their own roleguides. A team reads it when it touches its known-issues register.
23
+
24
+ ## Why this exists
25
+
26
+ Two teams could not write to their registers on 2026-09-06.
27
+ `mx-agent-surface-known-issues` reached 49,075 characters, and its next write returned exit 2,
28
+ "content is 51050 characters, over the 50000-character server limit".
29
+ `mx-agent-gateway-known-issues` reached 49,910 and was refused the same way.
30
+ [#457](https://github.com/memnexus-ai/mx-agent-framework/issues/457) records both refusals. A
31
+ team at the cap cannot record a finding at the moment it finds it. That is the worst moment to
32
+ lose one.
33
+
34
+ Named memories stop accepting writes at 50,000 characters. `core-api` enforces the cap
35
+ server-side and returns HTTP 413 (reported in
36
+ [#27](https://github.com/memnexus-ai/mx-agent-framework/issues/27), filed 2026-08-21, open).
37
+
38
+ Surface and gateway then cut their registers back by hand. Four registers, measured after those
39
+ cuts on 2026-09-06 with
40
+ `mx memories get --name <name> --format json | jq -r '.content | length'`:
41
+
42
+ | Named memory | Characters |
43
+ |---|---|
44
+ | `mx-agent-gateway-known-issues` | 47,827 |
45
+ | `mx-agent-surface-known-issues` | 42,519 |
46
+ | `mx-agent-bootstrap-known-issues` | 26,212 |
47
+ | `mx-agent-product-known-issues` | 13,241 |
48
+
49
+ All four sizes are under the cap. The refusals are resolved, and this standard prevents the
50
+ next one rather than ending a live failure.
51
+
52
+ One of the four is above the 45,000-character warning line: gateway, at 47,827. The warning
53
+ never fires.
54
+
55
+ That sentence read "Two of the four" until 2026-09-22, and it was wrong against the table four
56
+ lines above it. It was written while surface held 49,075 characters and it was not re-derived
57
+ after surface cut back to 42,519. Corrected here rather than deleted, because a figure that
58
+ contradicts its own table is the failure lesson L2 in `.mx-agent/lessons.md` exists to catch, and
59
+ this file is the one telling four teams to publish the command beside the figure.
60
+ `named-memory-write-guard.sh` does not warn on `--content-file` writes, and the roleguides
61
+ require that spelling (`mx-agent-system/roleguides/product-leader.md:588`, "Use
62
+ `--content-file`, written with the `Write` tool").
63
+ [#457](https://github.com/memnexus-ai/mx-agent-framework/issues/457) tracks the fix, owned by
64
+ bootstrap.
65
+
66
+ Registers also hold items that were never filed anywhere else.
67
+ [#27](https://github.com/memnexus-ai/mx-agent-framework/issues/27) states that unfiled backlog
68
+ is why two condensing passes recovered about 1,100 characters. The Rollout section below states
69
+ each team's filing count, its counting unit, and what that count excludes. Read the counts there.
70
+ This paragraph held four of them until 2026-09-22 and two had gone stale: bootstrap recounted 47
71
+ of 48 down to 46 of 48, and surface, recorded here as not having measured, reported 27 of 34 on
72
+ 2026-09-07.
73
+
74
+ [#27](https://github.com/memnexus-ai/mx-agent-framework/issues/27) also found three register
75
+ entries disagreeing with live issue state. One said OPEN where the issue was CLOSED, two said
76
+ CLOSED where the issues were OPEN. No check detects that today.
77
+
78
+ GitHub issues are not only a defect tracker. They are a durable, searchable, commentable record
79
+ for anything about the project, and every team and the product owner can read them.
80
+
81
+ GitHub issues are permanent, and this repository's visibility is one setting, so making the
82
+ repository public would publish every issue already filed.
83
+
84
+ ## Every known issue is a GitHub issue
85
+
86
+ File it. One exception, in the next paragraph. Nothing your team knows exists only in a memory.
87
+
88
+ One exception. An unfixed security finding, or an entry holding a credential, secret, token or
89
+ connection string, does not go in an issue. If an entry holds a credential value, rotate it
90
+ first, then file the entry with the value removed. Never paste a credential value into an issue.
91
+
92
+ **The private destination does not exist yet, so this exception defers rather than redirects.**
93
+ `gh api repos/memnexus-ai/mx-agent-framework/security-advisories` returns HTTP 404, run
94
+ 2026-09-22 by bootstrap from its worktree and by product from its own. The `gh` login holds
95
+ `admin: true` on this repository, so the 404 reports a disabled feature rather than a permission
96
+ this fleet lacks. Enabling it needs a decision nobody has taken, tracked in
97
+ [#479](https://github.com/memnexus-ai/mx-agent-framework/issues/479).
98
+
99
+ Until that path answers, an unfixed security finding stays in your register. Leave the entry
100
+ where it is, add one line saying it is held under this exception and naming
101
+ [#479](https://github.com/memnexus-ai/mx-agent-framework/issues/479), and exclude it from your
102
+ uncited count. It is not filing debt while it has nowhere to go. When the advisory path works,
103
+ file it there and put only the advisory link and a one-line title in the index.
104
+
105
+ This is the one case where the register keeps content rather than a pointer. Found by bootstrap,
106
+ which measured the endpoint rather than assuming the rollout worked.
107
+
108
+ Treat every issue body as readable by someone outside this company. That is the test, not the
109
+ repository's current setting. The product owner ruled on 2026-09-22, asked directly, that this
110
+ repository is to be treated as one that may become public. It is private today:
111
+ `gh repo view memnexus-ai/mx-agent-framework --json visibility` returns `PRIVATE`, run
112
+ 2026-09-22. The ruling governs anyway, because an issue filed today survives the setting that
113
+ makes it readable.
114
+
115
+ Anything you would have written in your known-issues register is an issue: a bug, a feature
116
+ request, an open question, an ownership gap, a correction to a claim your team published, a
117
+ dependency you filed on another team. The kind is a label. It is never a different store.
118
+
119
+ Label the kind with the labels the repository already has: `bug`, `enhancement`, `question`,
120
+ `documentation`, `duplicate`, `invalid`, `wontfix`, `help wanted`. Add the `team:<slug>` label
121
+ of the team that owns the work. Leave the team label off when ownership is the open question,
122
+ and say in the body that nobody owns it. The absence is the finding. For an issue that
123
+ corrects a claim your team published, use `documentation` and state the correction in the first
124
+ line. Do not create labels.
125
+
126
+ **Search before you open an issue.** Run
127
+ `gh issue list --search '<words>' --state all --limit 20` first. Type two to five plain words
128
+ from the entry's title. Do not paste entry text. Use single quotes, and leave out backticks, `$`,
129
+ quotes and backslashes, because bash runs a command inside double quotes. Never put a credential
130
+ value or the detail of a security finding in a search.
131
+
132
+ If an issue already covers the entry, cite that issue in the index line and open nothing. Before
133
+ you cut the entry, add any detail the issue lacks as a comment on it. If that issue is closed
134
+ and the entry is still open, reopen the issue if it carries your `team:<slug>` label. Otherwise
135
+ file a new one that names it, and comment on the closed issue with the new number. Bootstrap's
136
+ register lists its iteration-log size item as "no issue filed", and bootstrap's lead found
137
+ [#481](https://github.com/memnexus-ai/mx-agent-framework/issues/481) covers the same defect.
138
+ `gh issue view 481 --json title,state` returns `OPEN`, run 2026-09-26 by product. Following the
139
+ filing rule without the search would have opened a duplicate.
140
+
141
+ Filing what your team already holds is bounded work. The rollout section below states your
142
+ team's uncited count and the iteration close it files by.
143
+
144
+ ## The named memory is an index and nothing else
145
+
146
+ `mx-agent-<team>-known-issues` holds one line per open issue: the issue number, the title in
147
+ one line, and the status. Nothing else.
148
+
149
+ It holds no evidence, no reproduction steps, no decision, no history, no priority argument. If
150
+ a line holds detail that exists nowhere else, the issue is incomplete. Put the detail in the
151
+ issue, then cut the line back.
152
+
153
+ **A resolved item leaves the index.** When its issue closes, delete the line. Do not keep a
154
+ resolved footer and do not keep a line with status `closed`. A closed issue stays readable by
155
+ number forever, so the index loses nothing by dropping it, and a register that keeps its
156
+ resolved items grows without bound again. Bootstrap and surface both asked this rather than
157
+ assuming, which is what the directive asked for.
158
+
159
+ **A fixed item that never had an issue also leaves the index.** Delete the line and do not file
160
+ it. Your filing report records three things for it. Quote the item's heading verbatim. Name the
161
+ merged pull request with the output of `gh pr view <N> --json state,mergedAt`, or the command
162
+ and its output that shows the item resolved. Name the memory version you cut the line from. An issue opened only to be closed is work someone has to close by
163
+ hand ([#544](https://github.com/memnexus-ai/mx-agent-framework/issues/544)).
164
+
165
+ A security finding does not take this exit. File it as an issue and close it with the pull
166
+ request, so a durable record remains. An item any reviewer has classified as a security finding
167
+ is filed, not cut, unless the product owner releases it.
168
+
169
+ **A satellite memory follows the same rule.** A team holding practice lessons, deferred issues
170
+ or resolved issues in separate named memories files each open item as an issue and indexes it in
171
+ the one `mx-agent-<team>-known-issues` memory. Resolved satellites are deleted rather than
172
+ migrated. Surface holds three and raised it; this is the answer.
173
+
174
+ **An archive memory is the exception to both.** See below. An archive records what a team held
175
+ at a time and is never edited.
176
+
177
+ Do not delete this memory. `create.ts:682`, "TEAM_MEMORY_SUFFIXES", lists `known-issues`, and
178
+ `:701` matches the name by regex. Provisioning constructs `${memPrefix}${slug}-known-issues` in
179
+ six places; find them with `grep -n 'known-issues' mx-agent-system/cli/src/commands/create.ts`.
180
+ Removing the memory breaks team creation. Leave it in place and keep the index in it.
181
+
182
+ Those six construction sites carried bare line numbers until 2026-09-22, and all six went stale
183
+ within hours when `create.ts` grew by 58 lines on `main`. The claim survived and the pointers
184
+ did not, which is why this paragraph names a grep instead.
185
+
186
+ ## If your register will not accept a write, file before you cut
187
+
188
+ Take the entries with the most text and no issue number first. Skip any entry held under the
189
+ security exception above
190
+ ([#479](https://github.com/memnexus-ai/mx-agent-framework/issues/479)): it is neither searched
191
+ nor filed. Search for each other entry first, as "Every known issue is a GitHub issue" states.
192
+ Open an issue for each one the search did not find, copying the entry in full. Read the entry
193
+ before you paste it. Then replace the entry with its index line.
194
+
195
+ Never delete an entry before its issue exists and you have the number. Read the current register
196
+ with `mx memories get --name <memory> --format json`. It never writes. `mx-agent memory
197
+ archive-prep` never writes to MemNexus, and it does write two local draft files.
198
+
199
+ ## Archive memories stay as they are
200
+
201
+ An archive memory records what a team held at a time. Do not edit one, do not add to one, and
202
+ do not repair a citation inside one.
203
+
204
+ Open an issue for every archived item still open, and add it to the index. The archive keeps
205
+ its original text.
206
+
207
+ ## Re-read the index from GitHub before you rely on it
208
+
209
+ Status in the index comes from GitHub, never from what you remember writing.
210
+
211
+ At the start of an iteration that reads or writes the index, run
212
+ `gh issue view <N> --json number,title,state` for each issue number in your index. Correct a
213
+ line only when that issue returns a different state or title. Date the index. Nothing detects
214
+ this drift for you.
215
+
216
+ A `team:` label query is not that check. An issue the query does not return is an issue whose
217
+ label is missing, so add the label. Never delete an index line because a label query did not
218
+ return it. When you do list by label, pass `--limit 500`: `gh` stops at the limit and reports
219
+ nothing. This repository holds 290 issues, counted 2026-09-22 with
220
+ `gh issue list --state all --limit 1000 --json number --jq 'length'`.
221
+
222
+ ## Rollout: each team files its own uncited items
223
+
224
+ ### First step: backfill the `team:<slug>` label
225
+
226
+ Before a team runs the re-read above, it adds the `team:<slug>` label to every issue its index
227
+ already cites. Labelled issue counts, from
228
+ `gh issue list --label "team:$t" --state all --limit 500 --json number --jq 'length'` run
229
+ 2026-09-22: bootstrap 46, gateway 1, surface 0, product 4. Gateway's index cites a number in 22
230
+ items and surface's in 27, so those numbers exist and their labels do not. Some of those numbers
231
+ are pull requests, as the table below shows. The backfill comes first
232
+ because the re-read is unsafe until it is done. A team that read a label query as the state of
233
+ its register today would cut 22 good lines from gateway's index and 27 from surface's.
234
+
235
+ **"Cites an issue" means the item names a GitHub issue number. A pull request number alone does
236
+ not count.** Classify each number with
237
+ `gh api repos/memnexus-ai/mx-agent-framework/issues/<N> --jq .pull_request`, where `<N>` is the
238
+ bare integer. It prints an empty line for an issue and an object for a pull request. A number
239
+ that returns HTTP 404 names no issue in this repository. Only a `#N` token or an
240
+ `https://github.com/memnexus-ai/mx-agent-framework/issues/N` URL is a citation. An issue named
241
+ in prose without either, such as "issue 11", is not. An item citing both an issue and a pull
242
+ request cites an issue. An item that cites only pull requests is one of three things:
243
+
244
+ - Fixed: it leaves the index under the rule for a fixed item above. It is not filed.
245
+ - Already tracked: the search before filing finds an issue. Cite that issue. File nothing.
246
+ - Untracked and open: file it.
247
+
248
+ Your filing report states the PR-only count in those three groups, each with its command.
249
+
250
+ Bootstrap's count predates this definition, so its row is a bound until bootstrap re-measures.
251
+ Product measured the other three rows on 2026-10-12 under this definition. An item's block runs
252
+ from its heading to the next `###` or `##` line. A `#N` with no `owner/repo` before it is a
253
+ citation of this repository.
254
+
255
+ | Team | Unit counted | Cites an issue | Cites only a PR | Cites no number | Files by |
256
+ |---|---|---|---|---|---|
257
+ | bootstrap | bold bullets, `^\s*-\s+\*\*` | at most 53 of 56 | not measured | 2, plus 1 citation repair | its next iteration close |
258
+ | gateway | `### P1`, `### P2` and `### P3` heading blocks | 10 of 36 | 12 | 14 | its next iteration close |
259
+ | surface | `### KI-SURFACE-...` heading blocks | 21 of 32 | 4 | 7 | its next iteration close |
260
+ | product | `### N.` heading blocks | 10 of 16 | 0 | 6 | its next iteration close |
261
+
262
+ The three measured rows read `mx-agent-<team>-known-issues` with
263
+ `mx memories get --name <memory> --format json`: gateway version 25, surface version 33 and
264
+ product version 6, all last written 2026-09-06. Surface's 32 is the count of `^### KI-SURFACE-`
265
+ lines in that version. Surface reported 34 on 2026-09-07, and product cannot reproduce 34. No
266
+ team's filing count is in this table. It is the PR-only items left after the three-way split,
267
+ plus the no-number items the search does not find. Each team states it when it files.
268
+
269
+ The deadline is each team's next iteration close after this standard merges to `main`, not a
270
+ calendar date. Each team files its own uncited items. No team files for another. Product files
271
+ its own.
272
+
273
+ The table counts live registers only. It excludes every archive memory. An archived item still
274
+ open files by the same iteration close, under the archive rule above. Each team counts its own
275
+ archived open items when it files. Its filing report states that count and the command that
276
+ produced it. A team that files only its table number has not finished.
277
+
278
+ The security exception applies to archived items. An archived item that is an unfixed security
279
+ finding, or that holds a credential, is not filed. If it holds a credential value, rotate it, as
280
+ the exception above requires. Add an index line naming the archive, the item and
281
+ [#479](https://github.com/memnexus-ai/mx-agent-framework/issues/479), and leave it out of the
282
+ count your filing report states. State the number held separately. Read each archived item
283
+ before you paste it.
284
+
285
+ A bootstrap red-team reported uncited entries in `mx-agent-bootstrap-known-issues-archive-1` on
286
+ 2026-09-24, coordination message `1790271451742-0`. Neither bootstrap's lead nor product's lead
287
+ has verified that count, so this file does not state it.
288
+
289
+ Never add these four numbers together. Bootstrap counts bold bullets and the other three count
290
+ heading blocks, so a sum mixes units and states nothing.
291
+
292
+ **Product files all 6, including item 2, which is resolved.** A security-reviewer teammate
293
+ scanning product's register on 2026-09-22 classified item 2 as an unfixed security finding to
294
+ hold under the security exception in "Every known issue is a GitHub issue". This lead checked
295
+ its premise instead of accepting the classification. Item 2 states that no `team:` label exists, so no directive this
296
+ team issues can be complied with. `gh label list` returns `team:bootstrap`, `team:product`,
297
+ `team:gateway` and `team:surface`, run 2026-09-22. Issue
298
+ [#476](https://github.com/memnexus-ai/mx-agent-framework/issues/476) holds `team:product`, and
299
+ bootstrap resolved both of that directive's citations and acted on it the same day. The control
300
+ works, demonstrated rather than argued. Item 2 is fixed, so the hold for unfixed findings does
301
+ not apply to it. A reviewer classified it as a security finding, so it is filed, not cut. Product
302
+ files item 2 as an issue and closes it at filing, citing that `gh label list` output.
303
+
304
+ Five limits on the numbers above:
305
+
306
+ - An item whose defect lives in another project's tracker cites that tracker, with the repository
307
+ named, and counts as cited. Bootstrap holds one such item citing `#4734`, a Claude Code harness
308
+ issue. Filing a local duplicate for a defect no team here can fix creates an issue nobody can
309
+ close. Write the repository beside the number, as `anthropics/claude-code#4734`, so a bare
310
+ number is never ambiguous about which tracker it names.
311
+
312
+ - Bootstrap's row states a count of a different register version from the other three. Bootstrap
313
+ measured 53 of 56 against `mx-agent-bootstrap-known-issues` version 57 on 2026-09-22, with
314
+ `grep -cE '^\s*-\s+\*\*'` returning 56 and the same lines filtered by `#[0-9]{2,}` returning
315
+ 53. The other three rows state counts from 2026-09-06 and 2026-09-07. Bootstrap's register was
316
+ rewritten twice in between and grew from 48 items to 56, so the older figure of 46 of 48 and
317
+ this one measure different things rather than disagreeing. A product red-team reported at least
318
+ five uncited items against the version it read, and bootstrap cannot reproduce five against
319
+ version 57. Both numbers stay published with their versions beside them. Neither is withdrawn.
320
+ Of bootstrap's 3 uncited, 1 is a line naming an issue that exists,
321
+ [#470](https://github.com/memnexus-ai/mx-agent-framework/issues/470), without citing its
322
+ number. That is a citation repair rather than filing debt, and bootstrap found it.
323
+ - Superseded note, kept so the earlier reading stays traceable: this entry read "Bootstrap's 2 is
324
+ disputed. A product red-team reported at least five uncited items, and
325
+ bootstrap reproduced one or two. Nobody has reconciled the two counts. Bootstrap files what
326
+ it finds and reports the number it filed." Superseded 2026-09-22 by the entry above, after
327
+ bootstrap supplied its rule and its register version.
328
+ - Gateway's 36 excludes gateway's own archive memory, as every row excludes its team's
329
+ archives. The paragraph beginning "The table counts live registers only" gives archived items
330
+ their deadline.
331
+ - Surface holds three satellite memories, counted separately from the 32. Surface's
332
+ `resolved-issues` memory returns zero items under the `### KI-SURFACE-` unit and holds 6,654
333
+ characters, so it is unmeasured rather than empty. Surface measures it before it files.
334
+
335
+ Product's own register size was unreconciled and now is not. **Measure `content`. The cap applies
336
+ to nothing else.**
337
+
338
+ Product measured 13,241 characters and a product red-team measured 45,283 the same day. Both
339
+ were right about what they measured. `mx memories get --name mx-agent-product-known-issues
340
+ --format json | jq -r '.content | length'` returns 13,241, run 2026-09-22 and unchanged since
341
+ 2026-09-06. The whole JSON record returns 47,018 bytes the same day, and the difference is the
342
+ extracted graph the server stores beside the content: `claims` 13,996 bytes, `entities` 9,359,
343
+ `relationships` 2,340, `facts` 933. Those grow on their own as extraction runs, without a team
344
+ writing a word.
345
+
346
+ The cap governs `content`. [#457](https://github.com/memnexus-ai/mx-agent-framework/issues/457)
347
+ records the refusal text verbatim, "content is 51050 characters, over the 50000-character server
348
+ limit". So product's register is at 26% of the cap rather than at 91%, and the alarming figure
349
+ measured the envelope.
350
+
351
+ Any team sizing its register against the cap measures `.content | length` and nothing else. A team
352
+ that measures the record will believe it is near a limit it is nowhere near, and a team that
353
+ believes that will cut entries it did not need to cut.
354
+
355
+ ## What this standard does not change
356
+
357
+ `AGENTS.md` requires that all memories live in MemNexus and bans parallel memory stores. This
358
+ standard does not change that, and it does not create a parallel memory store. A known issue is
359
+ tracked work rather than a memory of what happened. The index stays in MemNexus and stays the
360
+ team's entry point, which is consistent with `AGENTS.md` naming MemNexus the sole memory
361
+ store. The wording in `AGENTS.md` belongs to that file's owner, and this standard does not edit
362
+ it.
363
+
364
+ Four roleguides describe the register as holding evidence, and those lines now describe an
365
+ index instead: `surface-leader.md:471`, `gateway-leader.md:569`, `bootstrap-leader.md:640`,
366
+ `product-leader.md:612` and `product-leader.md:688`. Each team edits its own roleguide. This
367
+ standard does not edit them.
368
+
369
+ [#356](https://github.com/memnexus-ai/mx-agent-framework/issues/356) reports that team-builder
370
+ leaves the `known-issues` memory unbounded. An index bounds it in practice.
371
+ [#356](https://github.com/memnexus-ai/mx-agent-framework/issues/356) and
372
+ [#457](https://github.com/memnexus-ai/mx-agent-framework/issues/457) both still need their
373
+ fixes.
374
+
375
+ ## One label is missing
376
+
377
+ No existing label marks an issue that corrects a claim the team published. `documentation` is
378
+ the closest, and it does not say a claim was withdrawn. A `correction` label would. Whoever
379
+ owns repository labels decides that; this standard tells agents to use `documentation` until
380
+ the label exists.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@memnexus-ai/mx-agent-cli",
3
- "version": "0.1.296-next.3",
3
+ "version": "0.1.296-next.4",
4
4
  "description": "CLI for creating and managing AI agent teams",
5
5
  "type": "module",
6
6
  "bin": {