@dreamforgestudiollc/emet 0.3.0 → 0.3.1

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.
package/.env.example CHANGED
@@ -94,8 +94,8 @@ EMET_SOURCE_TAGS=laptop,phone,cli
94
94
 
95
95
  # Optional. Address used by emet_error_report for the mailto draft and the
96
96
  # structured email a calling assistant can pass to its own mail tool. Unset
97
- # uses reports@example.com. That address is a placeholder, not a mailbox:
98
- # configure this to a real address, or the report is returned and goes nowhere.
97
+ # uses dreamforgestudio@mail.grokbot.com, the project's report inbox. Set it
98
+ # to your own address to keep reports in house.
99
99
  # EMET does not send mail. An empty string (a real empty environment
100
100
  # variable, not a blank line in this file) returns the report and no email.
101
101
  # The assistant may send the report only after showing it to you and getting
package/CHANGELOG.md CHANGED
@@ -5,6 +5,14 @@ All notable changes to EMET are listed here, newest first. The format follows
5
5
  [Semantic Versioning](https://semver.org/). EMET is still 0.x: the stored data shapes may
6
6
  change before 1.0.
7
7
 
8
+ ## 0.3.1 - 2026-10-21
9
+
10
+ - Changed: `EMET_REPORT_EMAIL` defaults to `dreamforgestudio@mail.grokbot.com`.
11
+ - Added: `scripts/verify-emet.mjs`, also `npm run verify`. Subcommands are `doctor`, `list`, `run`, and `feature`. `--json` prints one object. `--dry-run` skips a call that replaces stored text or hands out access, and says what it would have called. The command uses a temporary directory and the in-memory test database. It does not read `.env`. A tool that needs a service or setting a plain install does not have is reported as a gap. A run whose only problems are gaps exits 3. A failed tool exits 1.
12
+ - Changed: the Official MCP Registry description in `server.json` stays within the registry's 100-character limit and names stable error codes.
13
+ - Added: `docs/features/` is the feature map, one file per feature, including error codes, the error log, and `emet_error_report`. `tests/feature-map.test.js` fails if a registered tool is missing from the map.
14
+ - Added: `docs/DEVELOPMENT-PRACTICES.md`. Docs ship in the same pull request as the feature. A feature is checked by running `verify-emet`, not by tests alone. The feature map stays current. Every pull request gets two independent reviewers who cross-check each other's verdicts.
15
+
8
16
  ## 0.3.0 - 2026-10-20
9
17
 
10
18
  ### Added
package/README.md CHANGED
@@ -10,7 +10,7 @@ EMET is an MCP (Model Context Protocol) memory server, persistent shared memory
10
10
 
11
11
  **Website:** <https://dreamforgestudiollc.github.io/EMET/>
12
12
 
13
- See also: [CHANGELOG](CHANGELOG.md) · [CONTRIBUTING](CONTRIBUTING.md) · [SECURITY](SECURITY.md) · [Charter](CHARTER.md)
13
+ See also: [CHANGELOG](CHANGELOG.md) · [CONTRIBUTING](CONTRIBUTING.md) · [SECURITY](SECURITY.md) · [Charter](CHARTER.md) · [Feature map](docs/features/README.md) · [Development practices](docs/DEVELOPMENT-PRACTICES.md)
14
14
 
15
15
  ## What it does
16
16
 
@@ -24,7 +24,9 @@ See also: [CHANGELOG](CHANGELOG.md) · [CONTRIBUTING](CONTRIBUTING.md) · [SECUR
24
24
  - **Client-side GEM execution.** A GEM may declare a tool. EMET does not run that computation. EMET verifies the record, not the computation. The client runs the tool, and what is written back is checked the same way as any other write.
25
25
  - **Released flag.** A GEM is seated only when its released flag is the boolean true. Any other value is refused. A missing flag is refused except for a legacy manifest pinned by id, version, and file digests.
26
26
  - **Per-client attribution and approvals.** Every write is attributed to the client that made it. A new client is read-limited until it is approved. The approval is recorded.
27
- - **MIT.** Version 0.3.0. EMET is still 0.x: stored document shapes may change before 1.0. Pin a version if you depend on them.
27
+ - **Error codes and problem reports.** Every error carries a stable `EMET-<AREA>-<NNN>` code. An operational error log keeps 10,000 entries or 90 days, plus daily summaries. The owner-only `emet_error_report` returns the report and an email draft that you send yourself. See [Reporting a problem](#reporting-a-problem).
28
+ - **verify-emet and the feature map.** `npm run verify` runs `scripts/verify-emet.mjs` from a checkout. It starts EMET in a temporary directory on the in-memory test database, with no `.env`, and drives every registered tool. A tool that needs a service a plain install does not have is reported as a gap. A run whose only problems are gaps exits 3. A failed tool exits 1. The map is [docs/features/README.md](docs/features/README.md).
29
+ - **MIT.** Version 0.3.1. EMET is still 0.x: stored document shapes may change before 1.0. Pin a version if you depend on them.
28
30
 
29
31
  The store has one owner, and other people can join only through the optional Guest
30
32
  (read-only) and Member (read and write) access, both off by default.
@@ -774,7 +776,7 @@ enforcement: what is actually auto-approved is a host-side setting. See
774
776
 
775
777
  `emet_error_report` is owner-only and read-only. It reads the operational error log and returns the full report, a `mailto:` draft, and a structured email `{to, subject, body_text, short_id, version}`. EMET does not send mail and does not open a network connection for this tool.
776
778
 
777
- Read the report first. The draft is addressed to `EMET_REPORT_EMAIL`. When that variable is unset, the address is `reports@example.com`. That address is a placeholder, not a mailbox: configure `EMET_REPORT_EMAIL` to a real address, or the report is returned and goes nowhere. Set the variable to an empty string, or to anything other than one plain address, and the tool returns the report and no email.
779
+ Read the report first. The draft is addressed to `EMET_REPORT_EMAIL`. When that variable is unset, the address is `dreamforgestudio@mail.grokbot.com`, the project's report inbox. Set it to your own address to keep reports in house. Set it to an empty string, or to anything other than one plain address, and the tool returns the report and no email.
778
780
 
779
781
  A calling assistant that has its own email address may pass that structured email to its own email tool. The calling assistant may send this report only after showing the report to its user and getting their OK. EMET will not send it. The code table is [docs/ERROR-CODES.md](docs/ERROR-CODES.md), and the behavior is written up in [docs/ERROR-CODES-SPEC.md](docs/ERROR-CODES-SPEC.md).
780
782
 
@@ -0,0 +1,26 @@
1
+ # Development practices
2
+
3
+ How a change to EMET is specified, checked, and reviewed.
4
+
5
+ ## Docs ship with the feature
6
+
7
+ Write the feature page first, from the user's point of view, and land it in the same pull request as the code. The page lives in [docs/features](features/README.md): what the feature is, how a person reaches it, how to drive it, and what goes wrong. A tutorial, a how-to, a reference, and an explanation are different jobs. Do not fold them into one muddy page. The README and the site stay in step with that page when the change is something a user can see.
8
+
9
+ The feature map is part of the tree, so the next session can read it instead of rediscovering the product. `tests/feature-map.test.js` fails if a registered tool is missing from the map. Update the map in the same change that adds or renames a tool.
10
+
11
+ ## Verify by running
12
+
13
+ Tests pin behavior. They are not the whole check. `npm run verify` runs [scripts/verify-emet.mjs](../scripts/verify-emet.mjs), which brings EMET up in a temporary directory on the in-memory test database and drives the tools the way a plain install would. A tool that needs a service or a setting that process does not have is reported as a gap. Exit 3 is that report. Exit 1 is a tool that failed. Do not treat 3 as a crash, and do not stub a gap into a pass. A change to a feature is done when `verify-emet` has driven it, not when the unit tests alone are green.
14
+
15
+ Give the command a small, composable surface: `doctor`, `list`, `run`, and `feature`, plus `--json` and `--dry-run` on anything that replaces or hands out access. Errors say what to do instead.
16
+
17
+ ## Two reviewers
18
+
19
+ Every pull request gets two independent reviewers. Each one cross-checks the other's verdict against the diff and against a run of the change. A disagreement is resolved in the thread before merge.
20
+
21
+ ## Where this came from
22
+
23
+ These practices follow Lauren Tan's *The Complete Guide to pstack*: a verification command you can run, a feature map in the repo, and docs written before the implementation so the code has something to be checked against.
24
+
25
+ - Part 1: <https://x.com/poteto/status/2094457600259842065>
26
+ - Part 2: <https://x.com/poteto/status/2097732320606507506>
@@ -1,6 +1,6 @@
1
1
  # Error codes and the error report
2
2
 
3
- This is the behavior EMET 0.3.0 ships. The code table is generated from the registry: [ERROR-CODES.md](ERROR-CODES.md). A code’s meaning does not change. A removed code is added to the retired list, stays in that table, and its number is not reused.
3
+ This is the behavior EMET 0.3.1 ships. The code table is generated from the registry: [ERROR-CODES.md](ERROR-CODES.md). A code’s meaning does not change. A removed code is added to the retired list, stays in that table, and its number is not reused.
4
4
 
5
5
  ## Where the code goes
6
6
 
@@ -30,7 +30,7 @@ The result is, in order:
30
30
  2. A `mailto:` draft, when an address is set.
31
31
  3. A structured email `{to, subject, body_text, short_id, version}`, plus the mailto link, so a calling assistant can pass it to its own email tool.
32
32
 
33
- `to` is `EMET_REPORT_EMAIL`. When the variable is unset, the address is `reports@example.com`. An empty string means no email: the tool returns the report and `email: null`. Any other value is treated the same way unless it is one plain address: exactly one `@`, a local part of letters, digits, and `. _ + -` that does not start or end with a dot and does not contain `..`, and a domain of at least two labels separated by dots. A label is letters, digits, and `-`, does not start or end with `-`, and is not empty.
33
+ `to` is `EMET_REPORT_EMAIL`. When the variable is unset, the address is `dreamforgestudio@mail.grokbot.com`. An empty string means no email: the tool returns the report and `email: null`. Any other value is treated the same way unless it is one plain address: exactly one `@`, a local part of letters, digits, and `. _ + -` that does not start or end with a dot and does not contain `..`, and a domain of at least two labels separated by dots. A label is letters, digits, and `-`, does not start or end with `-`, and is not empty.
34
34
 
35
35
  The subject is `EMET error report <version> <6 hex characters>`. `body_text` is the full report shown above. The mailto body is that same text when it fits, and a shorter draft when it does not. The link is at most 1,800 characters. Totals stay when they fit. Recent lines are cut to the newest that fit, and the draft says so. The report in the tool output stays complete.
36
36
 
package/docs/SETUP.md CHANGED
@@ -349,7 +349,7 @@ the thing is doing its job.
349
349
 
350
350
  ## Error reports
351
351
 
352
- `emet_error_report` is owner-only and read-only. It returns the report and a draft. EMET does not send mail. The draft address is `EMET_REPORT_EMAIL`. When that variable is unset, the address is `reports@example.com`. That address is a placeholder, not a mailbox. Configure `EMET_REPORT_EMAIL` to a real address, or the report is returned and goes nowhere. An empty string, or any value that is not one plain address, returns the report and no email.
352
+ `emet_error_report` is owner-only and read-only. It returns the report and a draft. EMET does not send mail. The draft address is `EMET_REPORT_EMAIL`. When that variable is unset, the address is `dreamforgestudio@mail.grokbot.com`, the project's report inbox. Set it to your own address to keep reports in house. Set it to an empty string, or to anything other than one plain address, and the tool returns the report and no email.
353
353
 
354
354
  ## When it does not work
355
355
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@dreamforgestudiollc/emet",
3
- "version": "0.3.0",
4
- "description": "EMET 0.3.0 — Enduring Memory & Epistemic Tiers. An MCP memory server with persistent shared memory for AI agents, bot teams and chats: layered memory, verified writes, a verbatim transcript tier, per-client attribution and approvals, and client-side GEM execution. EMET verifies the record, not the computation. A GEM is seated only when its released flag is true.",
3
+ "version": "0.3.1",
4
+ "description": "EMET 0.3.1 — Enduring Memory & Epistemic Tiers. An MCP memory server with persistent shared memory for AI agents, bot teams and chats: layered memory, verified writes, a verbatim transcript tier, per-client attribution and approvals, and client-side GEM execution. EMET verifies the record, not the computation. A GEM is seated only when its released flag is true. Every error carries a stable code; the owner-only emet_error_report returns a report and an email draft the user sends. npm run verify drives the registered tools from a checkout, and docs/features is the map of every feature.",
5
5
  "keywords": [
6
6
  "agent-memory",
7
7
  "ai-agents",
@@ -65,6 +65,7 @@
65
65
  "start": "node src/index.js",
66
66
  "start:http": "node src/http-remote.js",
67
67
  "test": "node tests/run-all-tests.js",
68
+ "verify": "node scripts/verify-emet.mjs",
68
69
  "coverage": "node scripts/coverage.mjs"
69
70
  },
70
71
  "dependencies": {
package/server.json CHANGED
@@ -2,8 +2,8 @@
2
2
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
3
3
  "name": "io.github.dreamforgestudiollc/emet",
4
4
  "title": "EMET",
5
- "description": "0.3.0. Free MIT; no account, key, or payment. Verifies the record, not the computation.",
6
- "version": "0.3.0",
5
+ "description": "0.3.1. Free MIT; no account, key, or payment. Verifies record, not computation. Stable error codes.",
6
+ "version": "0.3.1",
7
7
  "websiteUrl": "https://dreamforgestudiollc.github.io/EMET/",
8
8
  "repository": {
9
9
  "url": "https://github.com/dreamforgestudiollc/EMET",
@@ -22,7 +22,7 @@
22
22
  "registryType": "npm",
23
23
  "registryBaseUrl": "https://registry.npmjs.org",
24
24
  "identifier": "@dreamforgestudiollc/emet",
25
- "version": "0.3.0",
25
+ "version": "0.3.1",
26
26
  "transport": {
27
27
  "type": "stdio"
28
28
  },
@@ -13,7 +13,7 @@ import { redactText } from './redact.js';
13
13
  import { queryErrorLog } from './error-log.js';
14
14
 
15
15
  export const SEND_INSTRUCTION = 'The calling assistant may send this report only after showing the report to its user and getting their OK.';
16
- export const DEFAULT_REPORT_EMAIL = 'reports@example.com';
16
+ export const DEFAULT_REPORT_EMAIL = 'dreamforgestudio@mail.grokbot.com';
17
17
  export const MAILTO_MAX = 1800;
18
18
 
19
19
  /**
package/src/version.js CHANGED
@@ -1,2 +1,2 @@
1
1
  /** The server's version, in one place. tests/version.test.js keeps it equal to package.json. */
2
- export const EMET_VERSION = '0.3.0';
2
+ export const EMET_VERSION = '0.3.1';