@urbankitstudio/atlas 0.6.46 → 0.6.47

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/CHANGELOG.md CHANGED
@@ -1,5 +1,22 @@
1
1
  # @urbankitstudio/atlas Changelog
2
2
 
3
+ ## 0.6.47 — 2026-10-26
4
+
5
+ No data change. The hosted API, the hosted MCP and the site's free tools now read `safeValues`: they keep
6
+ a flagged layer's row only when its flag cell is one of the listed safe values and, trimmed and
7
+ upper-cased, holds no marker value anywhere in it, whatever the marker's length. Every other row is
8
+ withheld as `county-redacted`, a NULL cell included, and so is every row of a layer whose flag lists no
9
+ safe values. That is the rule this package's README has advised since 0.6.46, up to padding: trailing
10
+ U+0020 spaces are ignored on both sides of a string safe value, and an integer safe value also matches
11
+ text that trims (JavaScript `trim`) to its decimal form, so the hosted reader also keeps unpadded or
12
+ whitespace-wrapped forms of a safe cell. None of those forms can carry a marker: the marker test reads the
13
+ cell itself, and validate-atlas refuses a safe value that holds one. On the 2026-10-25 measurements that
14
+ newly withholds Harris's 5,235 and Collin's 15,003 NULL-flag rows; Ector is unchanged. A withheld row is
15
+ never billed: PAYG never meters it, and a plan unit reserved before the row was found withheld is refunded.
16
+ When that refund cannot be confirmed, the unit still counts against the quota and the response says so
17
+ (`plan_quota.refund` on `enrich_address`, `refunded: false` on a bulk row, radius's `charged`). A pay-as-you-go replay of an MCP `enrich_address` operation already paid returns the stored result as it would be served today, withheld when its county now withholds it, keeping the original `billed`, `operation_id` and charge and charging nothing new. When the stored result's county cannot be established, that replay is withheld as `county-unresolved`, with owner, mailing address, site address, parcel id and its county fields null where the stored result has them (a field it lacks stays absent). When the fresh lookup is itself withheld as `county-redacted`, that is the reason returned instead, and the same fields stay withheld. The README and the `ConfidentialFlag` comment no longer say the hosted reader serves a NULL
18
+ cell as unflagged.
19
+
3
20
  ## 0.6.46 — 2026-10-26
4
21
 
5
22
  Every confidential-flagged record now lists the exact raw cells its layer holds for an UNFLAGGED owner, and
package/README.md CHANGED
@@ -291,9 +291,14 @@ filter in your own code trims. `UPPER(CAST(<field> AS VARCHAR(255)))` also runs
291
291
  on all three if you want the comparison case-blind. Measured 2026-10-25: Harris
292
292
  has 470,972 blank cells that hold spaces, and the clause keeps them; it also has
293
293
  5,235 NULL cells, and Collin has 15,003. A NULL cell fails the clause and the
294
- row drops out; a missing column makes the query fail. The hosted API serves a
295
- NULL cell as unflagged, so the SQL route and the hosted API differ on those rows
296
- (Harris 5,235 and Collin 15,003, measured 2026-10-25).
294
+ row drops out; a missing column makes the query fail. Since 0.6.47 the hosted API,
295
+ the hosted MCP and the site's free tools keep the same rows, plus unpadded or
296
+ whitespace-wrapped forms of a safe cell, none of which can carry a marker: they
297
+ ignore trailing spaces (U+0020) on both sides of a string safe value, match an
298
+ integer safe value against text that trims (JavaScript `trim`) to its decimal
299
+ form, withhold a cell that holds a listed value anywhere in it, whatever that
300
+ value's length, and withhold every row of a layer whose flag lists no safe
301
+ values. So they withhold those NULL rows too.
297
302
 
298
303
  Then AND `<field> IN (<safeValues>)`, with the column neither cast nor
299
304
  upper-cased: strings single-quoted with `'` doubled, integers bare, joined by
package/dist/index.d.cts CHANGED
@@ -233,10 +233,16 @@ interface SearchField {
233
233
  * blank cells hold spaces and both clauses keep them; Harris also has 5,235
234
234
  * NULL cells and Collin 15,003 (2026-10-25). A NULL cell fails both clauses
235
235
  * and the row drops out; a missing column makes the query fail. That is
236
- * fail-closed, unlike the hosted reader, which serves a null cell as "no flag
237
- * recorded" and does not read `safeValues` yet. Or apply the rule to each row
238
- * yourself. Request the column whenever you request the owner. The hosted API
239
- * and MCP withhold a flagged row with `withheld: "county-redacted"`.
236
+ * fail-closed. Since 0.6.47 the hosted reader (the hosted API, the hosted MCP
237
+ * and the site's free tools) keeps the same rows, plus unpadded or
238
+ * whitespace-wrapped forms of a safe cell, none of which can carry a marker: it
239
+ * ignores trailing spaces (U+0020) on both sides of a string safe value,
240
+ * matches an integer safe value against text that trims (JavaScript `trim`) to
241
+ * its decimal form, withholds a cell that holds a listed value anywhere in it,
242
+ * whatever that value's length, and withholds every row of a layer whose flag
243
+ * lists no safe values. Or apply the rule to each row yourself. Request the
244
+ * column whenever you request the owner. The hosted API and MCP withhold a
245
+ * flagged row with `withheld: "county-redacted"`.
240
246
  */
241
247
  interface ConfidentialFlag {
242
248
  field: string;
package/dist/index.d.ts CHANGED
@@ -233,10 +233,16 @@ interface SearchField {
233
233
  * blank cells hold spaces and both clauses keep them; Harris also has 5,235
234
234
  * NULL cells and Collin 15,003 (2026-10-25). A NULL cell fails both clauses
235
235
  * and the row drops out; a missing column makes the query fail. That is
236
- * fail-closed, unlike the hosted reader, which serves a null cell as "no flag
237
- * recorded" and does not read `safeValues` yet. Or apply the rule to each row
238
- * yourself. Request the column whenever you request the owner. The hosted API
239
- * and MCP withhold a flagged row with `withheld: "county-redacted"`.
236
+ * fail-closed. Since 0.6.47 the hosted reader (the hosted API, the hosted MCP
237
+ * and the site's free tools) keeps the same rows, plus unpadded or
238
+ * whitespace-wrapped forms of a safe cell, none of which can carry a marker: it
239
+ * ignores trailing spaces (U+0020) on both sides of a string safe value,
240
+ * matches an integer safe value against text that trims (JavaScript `trim`) to
241
+ * its decimal form, withholds a cell that holds a listed value anywhere in it,
242
+ * whatever that value's length, and withholds every row of a layer whose flag
243
+ * lists no safe values. Or apply the rule to each row yourself. Request the
244
+ * column whenever you request the owner. The hosted API and MCP withhold a
245
+ * flagged row with `withheld: "county-redacted"`.
240
246
  */
241
247
  interface ConfidentialFlag {
242
248
  field: string;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@urbankitstudio/atlas",
3
- "version": "0.6.46",
3
+ "version": "0.6.47",
4
4
  "description": "JS SDK for the UrbanKit County Parcel REST API Atlas: 503 counties across all 50 US states and DC, 498 verified public ArcGIS REST endpoints for county parcel data, with searchable field metadata, sample queries and license info, plus verified city code-violation, building-permit and zoning-case datasets.",
5
5
  "keywords": [
6
6
  "parcel",