@mailwoman/mcp 10.2.2 → 10.4.0

package/README.md

@@ -33,4 +33,4 @@ the `mailwoman data pull candidate` fix instead of an internal resolver error.
 }
 ```
 
-`--poi-db <path>` wires `mailwoman_poi_search` (and `mailwoman_parse`'s `poi: true` path) to a real database; omit it and those tools degrade gracefully to intent-only.
+`--poi-db <path>` wires `mailwoman_poi_search` (and `mailwoman_parse`'s `poi: true` path) to a real database. Without the flag, those tools return intent only.

package/lib/layer-guards.ts

@@ -4,7 +4,7 @@
  * @author Teffen Ellis, et al.
  *
  *   Decision 6 layer-absent guards — kept out of `cli.ts` in their own importable module so the
- *   branching itself has direct unit coverage (`layer-guards.test.ts`), not just
+ *   branching itself has direct unit coverage (`layer-guards.test.ts`), beyond
  *   "the tool handler passes an abstain through" (`tools.test.ts`'s stub-level dispatch tests). `cli.ts`
  *   top-level-`await`s a real stdio transport connection at import time, so IT can't be imported by vitest. These
  *   three functions have no such dependency (pure existence-check + open, or a thrown Error), so they live here and
@@ -54,7 +54,7 @@ export async function openBDCDatabaseIfPresent(
  * physical-plant categories can't be searched.
  *
  * `POILookup` is dynamically imported (matching `cli.ts`'s existing `resolver-wof-sqlite` laziness)
- * since it's only ever needed when a caller actually wires a poi.db.
+ * since it's only ever needed when a caller wires a poi.db.
  * `lookup` and `schemadb` share one `DatabaseSync` handle
  * (the agents.md "one connection, shared" convention) — a real poi.db's rows
  * and its `layer_manifest`/`layer_coverage` tables live in the same file in production,

package/out/layer-guards.d.ts

@@ -4,7 +4,7 @@
  * @author Teffen Ellis, et al.
  *
  *   Decision 6 layer-absent guards — kept out of `cli.ts` in their own importable module so the
- *   branching itself has direct unit coverage (`layer-guards.test.ts`), not just
+ *   branching itself has direct unit coverage (`layer-guards.test.ts`), beyond
  *   "the tool handler passes an abstain through" (`tools.test.ts`'s stub-level dispatch tests). `cli.ts`
  *   top-level-`await`s a real stdio transport connection at import time, so IT can't be imported by vitest. These
  *   three functions have no such dependency (pure existence-check + open, or a thrown Error), so they live here and
@@ -43,7 +43,7 @@ export declare function openBDCDatabaseIfPresent(databasePath: PathBuilderLike |
  * physical-plant categories can't be searched.
  *
  * `POILookup` is dynamically imported (matching `cli.ts`'s existing `resolver-wof-sqlite` laziness)
- * since it's only ever needed when a caller actually wires a poi.db.
+ * since it's only ever needed when a caller wires a poi.db.
  * `lookup` and `schemadb` share one `DatabaseSync` handle
  * (the agents.md "one connection, shared" convention) — a real poi.db's rows
  * and its `layer_manifest`/`layer_coverage` tables live in the same file in production,

package/out/layer-guards.js

@@ -4,7 +4,7 @@
  * @author Teffen Ellis, et al.
  *
  *   Decision 6 layer-absent guards — kept out of `cli.ts` in their own importable module so the
- *   branching itself has direct unit coverage (`layer-guards.test.ts`), not just
+ *   branching itself has direct unit coverage (`layer-guards.test.ts`), beyond
  *   "the tool handler passes an abstain through" (`tools.test.ts`'s stub-level dispatch tests). `cli.ts`
  *   top-level-`await`s a real stdio transport connection at import time, so IT can't be imported by vitest. These
  *   three functions have no such dependency (pure existence-check + open, or a thrown Error), so they live here and
@@ -45,7 +45,7 @@ export async function openBDCDatabaseIfPresent(databasePath) {
  * physical-plant categories can't be searched.
  *
  * `POILookup` is dynamically imported (matching `cli.ts`'s existing `resolver-wof-sqlite` laziness)
- * since it's only ever needed when a caller actually wires a poi.db.
+ * since it's only ever needed when a caller wires a poi.db.
  * `lookup` and `schemadb` share one `DatabaseSync` handle
  * (the agents.md "one connection, shared" convention) — a real poi.db's rows
  * and its `layer_manifest`/`layer_coverage` tables live in the same file in production,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mailwoman/mcp",
-  "version": "10.2.2",
+  "version": "10.4.0",
   "description": "MCP server — mailwoman's toolset for agents: address parsing and geocoding, POI search and Overpass export, layer manifests, plausibility checks, and FCC broadband and filer lookups.",
   "license": "AGPL-3.0-only OR LicenseRef-Commercial",
   "repository": {
@@ -88,17 +88,17 @@
     }
   },
   "dependencies": {
-    "@mailwoman/bdc": "10.2.2",
-    "@mailwoman/core": "10.2.2",
-    "@mailwoman/filer": "10.2.2",
-    "@mailwoman/neural": "10.2.2",
-    "@mailwoman/neural-weights-en-us": "10.2.2",
-    "@mailwoman/poi-taxonomy": "10.2.2",
-    "@mailwoman/resolver": "10.2.2",
-    "@mailwoman/resolver-wof-sqlite": "10.2.2",
-    "@mailwoman/sqlite": "10.2.2",
+    "@mailwoman/bdc": "10.4.0",
+    "@mailwoman/core": "10.4.0",
+    "@mailwoman/filer": "10.4.0",
+    "@mailwoman/neural": "10.4.0",
+    "@mailwoman/neural-weights-en-us": "10.4.0",
+    "@mailwoman/poi-taxonomy": "10.4.0",
+    "@mailwoman/resolver": "10.4.0",
+    "@mailwoman/resolver-wof-sqlite": "10.4.0",
+    "@mailwoman/sqlite": "10.4.0",
     "@modelcontextprotocol/sdk": "^1.32.1",
-    "mailwoman": "10.2.2",
+    "mailwoman": "10.4.0",
     "path-ts": "^2.5.0",
     "zod": "^4.6.5"
   }