@tileflow/dev 0.1.0-alpha.37 → 0.1.0-alpha.39

package/dist/{chunk-UTRO4IBQ.js → chunk-FOMTSCOP.js}

@@ -1,7 +1,7 @@
 import {
   TileflowAssetDirectoryError,
   resolveTileflowAssetDirectories
-} from "./chunk-7C4F6GAX.js";
+} from "./chunk-RTU7TD4M.js";
 import {
   isPathWithin
 } from "./chunk-D4OE4ITL.js";

package/dist/{chunk-7C4F6GAX.js → chunk-RTU7TD4M.js}

@@ -71,7 +71,9 @@ async function resolveTileflowAssetDirectories(directories, options) {
       let packageRoot;
       try {
         validatePackageDirectory(directory);
-        const requireFromProject = createRequire(resolve(realCwd, "__tileflow_config__.cjs"));
+        const requireFromProject = createRequire(
+          resolve(realBaseDirectory, "__tileflow_config__.cjs")
+        );
         let packageJson;
         try {
           packageJson = requireFromProject.resolve(`${directory.package}/package.json`);
@@ -120,7 +122,7 @@ async function resolveTileflowAssetDirectories(directories, options) {
         containmentRoot,
         packageOwned,
         realPath: realCandidate,
-        watch: !packageOwned
+        watch: !packageOwned || isPathInside(realCwd, realCandidate) && !realCandidate.split(/[\\/]/u).includes("node_modules")
       });
     } catch (error) {
       issues.push({

package/dist/fonts.js

@@ -4,8 +4,8 @@ import {
   getTileflowFontWatchPaths,
   prepareTileflowStyleFonts,
   replaceTileflowStyleFontSources
-} from "./chunk-UTRO4IBQ.js";
-import "./chunk-7C4F6GAX.js";
+} from "./chunk-FOMTSCOP.js";
+import "./chunk-RTU7TD4M.js";
 import "./chunk-D4OE4ITL.js";
 export {
   TileflowFontCompilationError,

package/dist/icons.js

@@ -17,8 +17,8 @@ import {
   storeTileflowIconSetArtifact,
   verifyTileflowIconArtifact,
   writeTileflowIconsLockfile
-} from "./chunk-5RT4CHSK.js";
-import "./chunk-7C4F6GAX.js";
+} from "./chunk-C4VPHZ3F.js";
+import "./chunk-RTU7TD4M.js";
 export {
   TileflowIconCompilationError,
   compileTileflowIconPackages,

package/dist/preview.js

@@ -272,8 +272,8 @@ function renderTileflowPreviewHtml(preview, basePath, initialStatus, isSemanticP
       import * as maplibregl from "${basePath}/__runtime/maplibre-gl.mjs";
       import {createPreviewObserver} from "${basePath}/__runtime/inspector-observer.js";
       import {loadTileflowStyleFonts} from "${basePath}/__runtime/tileflow-browser.js";
-      import {attachTileflowLabelPlacement} from "${basePath}/__runtime/tileflow-browser.js";
-      import {registerTileflowContourProtocol} from "${basePath}/__runtime/tileflow-browser.js";
+      import {attachTileflowHorizonQueries, attachTileflowLabelPlacement} from "${basePath}/__runtime/tileflow-browser.js";
+      import {registerTileflowContourProtocol, registerTileflowPathGroundProtocol} from "${basePath}/__runtime/tileflow-browser.js";
       import {registerTileflowPmtilesProtocol} from "${basePath}/__runtime/tileflow-browser.js";
       import {attachTileflowNauticalLights, attachTileflowNotices} from "${basePath}/__runtime/tileflow-browser.js";
       import {attachTileflowAtmosphere, tileflowMaxPitch} from "${basePath}/__runtime/tileflow-browser.js";
@@ -1674,6 +1674,7 @@ function renderTileflowPreviewHtml(preview, basePath, initialStatus, isSemanticP
         maplibregl.setWorkerCount?.(mapWorkerCount);
         await loadTileflowStyleFonts(styleUrl, {fontFaces: previewFontFaces});
         registerTileflowContourProtocol({addProtocol: maplibregl.addProtocol});
+        registerTileflowPathGroundProtocol({addProtocol: maplibregl.addProtocol});
         registerTileflowPmtilesProtocol({addProtocol: maplibregl.addProtocol});
         const map = new maplibregl.Map({
           canvasContextAttributes: tileflowCanvasContextAttributes({antialias: mapAntialias}),
@@ -1689,6 +1690,7 @@ function renderTileflowPreviewHtml(preview, basePath, initialStatus, isSemanticP
         attachTileflowNauticalLights(map);
         attachTileflowAtmosphere(map);
         attachTileflowLabelPlacement(map);
+        attachTileflowHorizonQueries(map);
         inspectorObserver?.attach(map);
         installMapBenchmark(map);
         if (window.parent === window) map.addControl(new maplibregl.NavigationControl(), "top-right");

package/dist/server.js

@@ -5,16 +5,16 @@ import {
   parseTileflowLineBackgroundGlyphPath,
   tileflowArtifactSessionSchemaVersion,
   tileflowLineBackgroundGlyphRoute
-} from "./chunk-UKWAQKLH.js";
+} from "./chunk-AVJMTXW5.js";
 import {
   getTileflowAssetBasePath,
   getTileflowAssetFileName,
   joinTileflowPublicUrl,
   normalizeTileflowBasePath,
   resolveTileflowArtifactPublicUrls
-} from "./chunk-UTRO4IBQ.js";
-import "./chunk-5RT4CHSK.js";
-import "./chunk-7C4F6GAX.js";
+} from "./chunk-FOMTSCOP.js";
+import "./chunk-C4VPHZ3F.js";
+import "./chunk-RTU7TD4M.js";
 import {
   TileflowStyleValidationError
 } from "./chunk-KDFTE4Q5.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tileflow/dev",
-  "version": "0.1.0-alpha.37",
+  "version": "0.1.0-alpha.39",
   "license": "Apache-2.0",
   "description": "Node development utilities for Tileflow configs and builds.",
   "type": "module",
@@ -27,7 +27,6 @@
   "files": [
     "dist",
     "ui-fonts",
-    "docs",
     "THIRD_PARTY_NOTICES.md",
     "LICENSE"
   ],
@@ -84,8 +83,8 @@
   "dependencies": {
     "@mapbox/vector-tile": "3.0.0",
     "@maplibre/maplibre-gl-style-spec": "26.4.4",
-    "@tileflow/core": ">=0.1.0-alpha.40 <0.1.0-beta.0",
-    "chokidar": "4.0.3",
+    "@tileflow/core": ">=0.1.0-alpha.43 <0.1.0-beta.0",
+    "chokidar": "6.0.0",
     "fontkit": "2.0.4",
     "jiti": "^2.7.0",
     "maplibre-gl": "6.13.0",
@@ -96,7 +95,7 @@
     "three": "0.185.1"
   },
   "devDependencies": {
-    "@tileflow/maps": "0.1.0-alpha.14"
+    "@tileflow/maps": "0.1.0-alpha.17"
   },
   "optionalDependencies": {
     "sharp": "0.35.5"

package/docs/artifact-lifecycle.md

@@ -1,152 +0,0 @@
-# Artifact lifecycle
-
-Start with the [@tileflow/dev guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/dev/README.md) for installation and a complete first example.
-
-Node utilities used by the Tileflow CLI and build integrations.
-
-Most apps should use `tileflow`, `@tileflow/vite`, or `@tileflow/next` directly. Use this
-package when you are building a custom dev server, bundler plugin, or deployment adapter that needs
-to load and compile the single map exported by `tileflow.config.ts`.
-
-```ts
-import {createTileflowBuildArtifacts} from '@tileflow/dev/artifacts';
-
-const artifacts = await createTileflowBuildArtifacts({
-  config: 'tileflow.config.ts',
-});
-
-try {
-  // Serve, capture, or write this exact generation.
-} finally {
-  await artifacts.dispose?.();
-}
-```
-
-The integration surfaces are deliberately split: use `@tileflow/dev/artifacts` for source
-preparation and production outputs, `@tileflow/dev/server` for HTTP development handling,
-`@tileflow/dev/icons` for icon compilation, `@tileflow/dev/inspect` for safe resolved-config and
-bounded feature inspection, `@tileflow/dev/validation` for structured diagnostics, and
-`@tileflow/dev/preview` only for the local preview contract. The package has no root entry point.
-
-Artifact construction is an explicit `source map → resolved map → prepared map → ArtifactPlan`
-pipeline. Map inheritance resolves before its ordered local/package icon and font directories are
-prepared, and before the result reaches the core style compiler. The Node layer may normalize
-the map into an internal build catalog, but that catalog is orchestration state rather than another
-public authoring model. The plan exposes its complete files and observed input graph, so build
-adapters emit and watch the same generation instead of reconstructing either list themselves. Production manifests
-point to content-addressed `generations/<sha256>/...` theme styles and sprites; those immutable files are
-installed before the manifest pointer changes. Stable style paths are
-`styles/<map>/<theme>.json`; every manifest lookup resolves a concrete theme. The disk writer also stages the complete plan,
-records a managed-file inventory, rolls back caught filesystem failures, and removes only stale
-files named by its previous valid inventory. Stable `styles/` and `icons/` paths remain available,
-but generation-consistent consumers resolve maps through `manifest.json`.
-
-A local `hostedTileset()` path remains user-owned input. Dev performs bounded header, root-directory,
-and metadata checks, then creates an opaque immutable snapshot under
-`.tileflow/cache/pmtiles-snapshots/v1/`, using copy-on-write cloning when available and a safe copy
-otherwise. It does not hash the complete archive or traverse every leaf directory. Dev and Capture
-read only that snapshot. The current generation and already-started acquisitions retain references;
-a replaced generation accepts no new acquisitions and is collected after its last acquisition.
-The Style-facing path remains `tilesets/<logical-id>.pmtiles` across generations; physical snapshot
-identity stays out of Style JSON. Standalone Capture retains one generation for the complete render.
-Application Capture delegates PMTiles reads to the application's development server, where each
-range request retains its generation until that response is prepared; it does not lease one
-generation for the complete capture. Strong generation ETags make a cached PMTiles read restart if
-current changes between its ranges. Invalid edits keep the prior valid generation.
-
-Production writers reject unresolved local PMTiles instead of copying, content-addressing,
-deduplicating, retaining, or publishing them. Production data therefore requires an explicit
-`tileset publish` operation or an application-owned PMTiles location. Managed publication owns its
-separate exhaustive validation and version lifecycle. Startup removes snapshot generations owned
-by dead processes, and symlinked snapshot-store boundaries are rejected.
-
-Every plan also emits canonical `build-manifest.json` (schema version 1). For each map it records
-the leaf `mapVersion`, resolved lineage, effective icon/font source identities, semantic compiler ABI, and
-one entry per concrete theme with `colorScheme`, identity, inferred legacy `dataRequirements`,
-multi-source `sourceRequirements`, and `styleSha256`. The multi-source contract records each
-referenced vector source independently and records raster DEM source ID, encoding, and tile size;
-it therefore distinguishes Bathymetry vector bands from optional relief without inventing vector
-fields. `mapRevisionSha256` identifies the effective cartographic definition after `extends`;
-`assetSetSha256` for that map's generated runtime resources. Data requirements are derived from the
-final Style layers and fields rather than copied from a manually maintained allowlist, so disabled
-or overridden modules do not claim data they no longer use. Maps use the single implicit semantic
-compiler; its ABI remains a separate `semanticCompiler: {name, version}` build-manifest axis.
-
-The map revision is versioned and domain-separated. It contains the resolved cartographic design,
-semantic language version, effective public module/render-stack design, and effective icon/font
-identities. Map `id`, `name`, editorial `mapVersion`, default `view`, capture `scenes`, package
-SemVer, compiler ABI, local paths, timestamps, generated sprite/font output, and a
-concrete resolution of a floating World selector are deliberately outside it. Changing a shadowed
-ancestor does not change the revision; changing an effective cartographic override or source asset
-does. Lineage and the leaf `mapVersion` remain beside the hash for traceability, and Style JSON owns
-its compiled-output identity. Hosted browser policy is managed outside repository artifacts. The
-top-level `provenance` block records the exact participating Tileflow package versions and the
-nearest package-manager lockfile's format and content hash, without embedding its local path;
-provenance remains outside every map revision. The same portable block is available to Hosted
-adapters through
-`createTileflowBuildProvenance(cwd)`. The dev server exposes the complete document at
-`/build-manifest.json`.
-
-`createTileflowStyle`, `createTileflowStyles`, and artifact construction all enforce the same
-recursive JSON-value invariant and MapLibre style-spec semantics without fetching remote resources.
-The family API returns `styles[map][theme]`; it never flattens a default theme into a map alias.
-Invalid output throws `TileflowStyleValidationError` with at most 32 deterministic
-`map`/`path`/`message` issues; layer indexes are projected to stable layer IDs.
-
-For a watched, last-known-good integration, use one artifact session rather than recompiling each
-request independently:
-
-```ts
-import {createTileflowArtifactSession} from '@tileflow/dev/artifacts';
-
-const session = await createTileflowArtifactSession({
-  config: 'tileflow.config.ts',
-  watch: true,
-});
-
-const unsubscribe = session.subscribe((state) => {
-  // building -> ready, or invalid while getLastGoodArtifacts() remains available
-  console.log(state.status, state.generation);
-});
-
-unsubscribe();
-await session.close();
-```
-
-`getState()` and `getLastGoodArtifacts()` are borrowed synchronous views. Before starting async
-work, call `session.acquireArtifacts(generation?)` and release the returned acquisition in `finally`.
-A replacement stops new acquisitions of the old generation and deletes its snapshot after the last
-release. `close()` waits for outstanding acquisitions.
-
-The bounded watcher follows the config, transitive local TypeScript/JavaScript/JSON imports, and
-effective local icon/font directory inputs. Generations are monotonic, overlapping refreshes are latest-wins, invalid
-edits retain the last good snapshot, and caller-supplied output directories can be ignored to avoid
-feedback loops. `tileflow preview`, `capture --watch`, and
-framework adapters use this shared status
-vocabulary. The built-in preview reloads after its live event stream reconnects following a server
-restart, even when the replacement process begins again at generation 1.
-
-Custom preview servers use the exported map or one of its standalone scenes:
-
-```ts
-import {createTileflowDevRequestHandler} from '@tileflow/dev/server';
-
-const fetch = createTileflowDevRequestHandler({
-  config: 'tileflow.config.ts',
-  scene: 'madrid-mobile',
-});
-
-// On server shutdown:
-await fetch.close();
-```
-
-The handler does not close a caller-owned session.
-
-Map preview uses the exported map's `view` and accepts one concrete `theme`; scene preview uses its
-committed concrete theme, camera, and CSS viewport metadata from that same map. A scene does not
-repeat the map ID because its owner is implicit.
-`resolveTileflowPreview()` exposes the validated selection for custom integrations.
-Application-target scenes remain the responsibility of the application's development server. The
-built-in preview records longitude, latitude, zoom, bearing, and pitch in the current URL, so browser
-refreshes and config-triggered reloads return to the same view. Removing those query parameters
-restores the configured camera.

package/docs/beacon-map-audits.md

@@ -1,145 +0,0 @@
-# Beacon map audits (legacy)
-
-The Beacon scoring and tour interface has been replaced by **Diagnostics**. See
-[Map design diagnostics](./map-design-diagnostics.md) for the current workflow. This document
-describes historical audit reports; its scores are not comparable with Diagnostics findings.
-
-Open `tileflow preview`, select **Beacon**, choose **Desktop** or **Mobile** and
-**Active tour** (default), **Quick check** or **All zooms**, then **Run audit**. The report includes 48 checks grouped into Rendering (9), Loading
-(8), Legibility (8), Accessibility (8), Cartography (7) and Integrity (8). Expand a result for its
-measured value, target, evidence and suggested fix. Findings open Layers, Tiles or Debug. **Copy
-context for agent** copies the bounded report; it does not upload it.
-
-## Scope and restoration
-
-Active tour follows a deterministic route through the current view, London, New York, Tokyo,
-Nairobi and São Paulo. Each location has an overview and a detailed view, with zoom, bearing and
-pitch changes within the map's camera limits. Destinations outside explicit map bounds are skipped
-and listed in coverage. The current theme stays active; this route does not cover every theme.
-
-The tour has a 60-second budget: up to 55 seconds for navigation and sampling, with the remainder
-reserved for diagnostics. Each stop measures a 1.2-second flight, waits up to two seconds for tiles,
-then samples up to 2.4 seconds of continuous settled repaints. On a responsive map the run usually
-takes 45–60 seconds. Slow loading can exhaust the budget: remaining views are explicitly unmeasured,
-not passed. Synchronous analysis and restoration may add a small overhead. Reduced-motion settings
-replace flights with jumps; the report does not claim an animated navigation measurement then.
-
-**Tour measurements** lists the actual camera, moving/settled p95 frame intervals, sample counts,
-remaining tile wait after navigation, and total readiness including navigation for each view.
-Loading scores use the remaining wait, excluding scripted animation; any timed-out view fails
-readiness. A p95 requires at least 30 intervals; coverage flags fewer than 60 settled
-intervals. A view that did not finish loading before sampling receives no settled performance score.
-The rendering check uses the worst qualifying per-view p95, so a slow location is not hidden by an
-average across fast locations. Long stalls are retained. These measurements include browser
-scheduling and other work on the machine, rather than isolated GPU execution time.
-
-Quick check samples the current camera and concrete theme for about three seconds. It is useful
-for static style checks and a short settled rendering sample. All zooms visits each integer zoom
-from 0 through 22 within map limits at the same geographic centre, for every registered theme and
-time-of-day variant. It waits up to five seconds for readiness and samples 150 ms per view. This
-exhaustive scope can take several minutes; it is not the one-minute navigation benchmark. Use
-**New audit** from a result to change scope or viewport.
-
-Desktop uses an actual 1280×800 CSS iframe viewport; Mobile uses 390×844. The iframe is scaled to
-fit the workspace. CPU, GPU and network are those of the current computer: this is not phone
-hardware emulation. No cache clearing, network throttling or cold navigation occurs.
-
-Camera, viewport, pixel ratio, overlays and scene are restored after completion or cancellation.
-Moving the map interrupts the audit and keeps the user's camera. Leaving Beacon cancels the run.
-A map replacement invalidates the run. Reports and preview changes stay local and in memory.
-
-## Measurements and limits
-
-- **Rendering:** inter-render p95 during continuous repaints (moving and settled windows for Active tour), native overdraw samples (saturating at
-  8 passes), eligible layer count, intercepted WebGL draw calls, CPU placement time, data-driven
-  paint-rule count, custom-renderer CPU submission time, and an observable GPU allocation estimate.
-  CPU submission is not GPU execution time. Readbacks and feature inspection are outside the frame
-  sample. GPU memory excludes inaccessible allocations; a low estimate is informational.
-- **Loading:** unused source-layer MVT message bytes, original map-load event time, individual tile
-  sizes when exposed, view readiness, per-view transfer and request counts, compression and cache
-  observations. PMTiles archive ranges are not individual tile sizes. Resource Timing cannot prove
-  Cache-Control policy. Cached audit views are not a fresh visitor estimate.
-- **Legibility:** observed text-placement rejections, line-label candidates, nearby repeated label
-  anchors, a scored text-size budget, approximate density, halos, configured line curvature and
-  requested language-field coverage. Rejections can result from collisions, offscreen placement or
-  line fit; the report does not pretend to know the renderer's exact rejection cause.
-- **Accessibility:** sampled text contrast in current/night/other themes, color-vision simulation
-  heuristics, static non-text contrast, categorical color-only rules, the system motion preference,
-  and sampled label retention after temporarily setting the real canvas ratio to 3×. Contrast uses
-  evaluated colors and supported flat fill/halo backgrounds. Raster, 3D and unresolved backgrounds
-  are excluded. This is diagnostic evidence, not accessibility certification.
-- **Cartography:** enabled zoom-range gaps, potential abrupt layer entry, road and place hierarchy
-  heuristics, scored size-rule continuity, unchanged eligible-layer counts and sampled fill coverage.
-  Naming-based hierarchy checks explicitly identify their inferred roles and exclude unmatched IDs.
-- **Integrity:** missing icon references, actual theme coverage, hidden-layer source residency,
-  cached missing glyphs, unresolved expressions, locally unmatched filters, style-spec validation
-  and retained runtime/resource errors. Resident data is bounded; zero local matches does not mean
-  a filter never matches globally.
-
-Samples are bounded to 4,000 rendered query results, 100 labels and 64 resident vector tiles per
-view; feature expression checks use up to 24 candidates spread across the bounded source sample per
-layer. Filter evidence counts only the candidates actually evaluated. Geometry is discarded after
-observation. All-zoom style snapshots are shared per theme. Custom renderer and private MapLibre
-observations are version-isolated and can be unavailable on unsupported renderers.
-
-## Scores and useful comparisons
-
-Category scores average checks with a measured score. Overall score averages measured categories.
-Informational and unavailable checks are excluded. Legibility and Cartography show a numeric score
-when eligible samples exist, together with the specific score basis and sample count. Each currently
-has one scored benchmark; its other checks remain diagnostic. Their scores do not assess the entire
-visual quality of a map.
-A category with no measurable scores shows **—**. For numeric
-budgets, meeting the displayed target scores 100; exceeding it by up to 1.5× scores 70, by up to 2×
-scores 45, and beyond that scores 0. Minimum targets invert the ratio. Structural counts and cartographic heuristics are explicitly marked **Diagnostic · not scored**.
-These include expression counts, rejected candidates, localized name fields, halos, fill coverage
-and locally unmatched filters. They remain visible as evidence without asserting a defect.
-Error scoring includes only resources and runtime errors observed during the audit, not prior session failures. A high score does not establish global map quality.
-
-The two quality benchmarks use an explicit percentage, rather than the generic budget tiers:
-
-- **Legibility / Text-size budget:** percentage of sampled labels whose evaluated `text-size` is
-  at least 10 CSS px. The threshold is a design budget, not an accessibility standard.
-  The bounded sample rotates between rendered symbol layers so dense POI layers do not monopolize it.
-  Font metrics, formatted section scaling, script, perspective and final glyph rasterization are not measured.
-  Unresolved expressions are excluded; their renderer fallback does not count as a passing size.
-- **Cartography / Size-rule continuity:** percentage of sampled layer/view size rules without a
-  jump exceeding both 1 px and 25% of the smaller size (with a 1 px denominator floor). For line
-  width, text size and circle radius, evaluate immediately around the actual zoom stops at
-  `stop ± 0.0001`, within the layer and camera zoom bounds. Continuous interpolation and physical
-  width scaling pass, even when sizes double between integer zooms. Changes at layer entry/exit,
-  filtered-out features and stops with opacity at or below 1% on either side are excluded.
-  Each ready view checks up to 128 visible layers, four feature contexts per layer and 128 stops
-  per rule. Missing or oversized evaluations are excluded. This measures authored rule continuity,
-  not final GPU pixels, label placement or transition animations. Intentional steps can exceed
-  the budget and should be reviewed before changing them.
-
-Only views that finished loading contribute to these scores. Each check exports `sample` with
-`passed`, `total`, `skipped` and `unit`; category `scoreBasis` identifies what its number represents.
-An observed outlier remains a warning even when rounding produces a high percentage. Findings
-include the layer and camera, with the exact zoom stop for a size jump. No eligible samples means
-unavailable, never an automatic 100. Repeated features in different views are separate observations.
-
-Repeat with the same view, scope, device, cache conditions and browser load when comparing changes.
-Review the evidence before acting on a warning. Copying findings supplies an agent with concrete
-layer IDs, camera context, measured values, coverage limits and suggested investigation steps.
-
-## Reproducible reports and future automation
-
-Reports use `version: 4`, `scoring: "measured-evidence-v3"` and identify the deterministic tour as `protocol: "active-tour-v1"`.
-Scenarios carry stable IDs, location, actual camera, theme, frame sample counts, p95, long-frame
-fraction, maximum frame interval, `tileWaitMs` after navigation, end-to-end `readyMs` and observed
-network transfer. Policy v2 excludes scripted camera time from loading scores; v1 included it.
-Policy v3 adds the sampled text-size and rule-continuity benchmarks described above; v2 left both
-categories entirely diagnostic. Old reports retain their original scores and must be rerun to use v3.
-`plannedViews` and
-`budgetExhausted` distinguish completed coverage from a partial run. Camera, viewport, DPR, duration
-and warnings accompany the scores. Change the protocol identifier when its itinerary or sampling
-rules change. The scoring policy is versioned separately: do not compare aggregate scores across
-policies. The original Active tour itinerary, timing windows and thresholds for measured frame
-performance are unchanged. There is no CI runner or GitHub integration in this feature.
-
-For future comparisons, keep protocol, map revision, initial view, browser/device, viewport, theme,
-DPR and cache conditions fixed. A single one-minute run is a diagnostic sample; repeated runs on a
-controlled worker are needed before setting regression gates. The tour does not clear caches,
-emulate mobile hardware, or prove worldwide coverage from six locations.

package/docs/bounded-pmtiles-resource-inspection.md

@@ -1,21 +0,0 @@
-# Bounded PMTiles resource inspection
-
-Start with the [@tileflow/dev guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/dev/README.md) for installation and a complete first example.
-
-Node tooling can inspect one local PMTiles archive without reading it completely:
-
-```ts
-import {inspectTileflowPmtiles} from '@tileflow/dev/tilesets';
-
-const inspection = await inspectTileflowPmtiles('./data/stores.pmtiles', {
-  includeValues: ['category', 'status'],
-});
-```
-
-Inspection schema 1 separates the authoritative PMTiles header and TileJSON `vector_layers` metadata
-from deterministic bounded MVT observations. Each sampled field reports present/missing feature
-counts, observed primitive types, capped distinct-value cardinality, numeric min/max, and explicit
-truncation. Values are returned only for requested portable field names, with at most 32 requested
-fields, 16 values per field, and 256 characters per string. Sampling reads at most eight tiles,
-20,000 features, or 24 MB of tile data; `sample: false` returns only authoritative metadata and does
-not accept `includeValues`.

package/docs/bounded-vector-feature-inspection.md

@@ -1,99 +0,0 @@
-# Bounded vector-feature inspection
-
-Start with the [@tileflow/dev guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/dev/README.md) for installation and a complete first example.
-
-Custom Node tooling can inspect only the features visible near a configured camera without opening
-a browser:
-
-```ts
-import {inspectTileflowFeatures} from '@tileflow/dev/inspect';
-
-const internalCatalog = artifacts.project;
-const inspection = await inspectTileflowFeatures(internalCatalog, 'madrid', {
-  center: [-3.6927512, 40.4086555],
-  zoom: 16,
-  sourceLayers: ['poi'],
-  properties: ['name', 'category', 'type', 'icon', 'filter_rank', 'size_rank'],
-  width: 512,
-  height: 512,
-  limit: 100,
-});
-```
-
-The inspector supports ordinary HTTP(S) vector sources and TileJSON. It bounds viewport, tile
-count, individual/total bytes, scanned and returned features, property count/string lengths, and
-request time; results are deduplicated and sorted deterministically. Output contains projected
-properties, geometry summaries, safe origin/path metadata, and the configured source revision or
-`null`. It never emits URL queries, credentials, hidden properties, response bodies, or absolute
-paths. PMTiles and authenticated provider adapters are not currently supported by this primitive.
-
-Deployment adapters can compile the same sources without writing them to disk:
-
-```ts
-import {compileTileflowIconPackages} from '@tileflow/dev/icons';
-
-const internalCatalog = artifacts.project;
-const result = await compileTileflowIconPackages(internalCatalog, {
-  cwd: process.cwd(),
-  target: 'hosted',
-});
-```
-
-Streets declares `[streetsIcons]` and keeps light/dark image-token targets in that one closure.
-Baedeker, Cívica, 1777, Siegfried, Soundings, and Blueprint declare only
-`[baedekerIcons]`, `[civicaIcons]`, `[map1777Icons]`, `[siegfriedIcons]`,
-`[soundingsIcons]`, and `[blueprintIcons]`, respectively. No official root composes another map's assets even though all
-use the semantic compiler ABI. Baedeker's directory contains eight original travel-atlas patterns;
-its browser-derived Mapterhorn contours use runtime terrain tiles and are not part of the icon
-package. Soundings owns twenty-seven original nautical symbols and
-patterns. Blueprint owns four technical blueprint patterns and one schematic POI node; its
-unbundled Mapterhorn contours remain runtime terrain, and its text uses the canonical Noto Sans
-glyph provider. An application map may inherit a root's exact array, replace it, clear it with `[]`,
-or compose it explicitly with a spread.
-`modules.poi.icons: false` or a disabled POI module suppresses POI icon layers without moving asset
-ownership into dev. POI density is the numeric producer threshold 1–5; it is not an asset-provider
-preset.
-
-The hosted target enforces repository containment, portable icon IDs, safe SVG
-references, deterministic ordering, and the public package limits. Package-owned directories are
-trusted only inside their declared owning package and are exempt from config working-tree
-containment. It returns deduplicated generated files plus a canonical manifest/content hash. Upload
-only those generated files: source icons and absolute paths remain local.
-
-The version-1 manifest includes `renderedIcons` in the exact sorted `iconNames` order. Each entry
-contains SHA-256 digests for the normalized 1x and 2x RGBA cell. The digest framing includes its
-density and dimensions, zeroes RGB only where alpha is zero, and excludes filenames/source bytes.
-The package content hash still covers the complete canonical manifest, including all four encoded
-file hashes. Consumers can therefore distinguish a visible per-icon change from an atlas-layout or
-encoding-only package change without receiving the original SVG/raster file.
-
-`compileTileflowIconPackages` retains the exact RGBA cells used to assemble each atlas, so its
-pixel digests describe delivered pixels rather than a second render. Hosted upload services must
-decode the submitted PNGs and reconstruct those digests independently; client-authored manifest
-analysis is not authoritative.
-
-Custom Node tooling can inspect the same local pipeline without walking or decoding source files a
-second time:
-
-```ts
-import {inspectTileflowIconCatalogs} from '@tileflow/dev/icons';
-
-const internalCatalog = artifacts.project;
-const inspection = await inspectTileflowIconCatalogs(internalCatalog, {
-  cwd: process.cwd(),
-  mapNames: ['madrid'],
-});
-```
-
-The result keeps one catalog per distinct ordered directory composition, the exact winning source
-for every final ID, explicit same-ID replacements, config-relative source metadata, exact atlas rectangles,
-both manifest pixel digests, and the shared compiled package. `icons: []` is represented as an
-absent catalog. This is a local-authoring integration surface: use the hosted compilation target
-separately for deployment compatibility, and project only the metadata needed by an external
-protocol rather than serializing generated byte arrays accidentally.
-
-This package is public, but it is an integration layer. Styling primitives live in
-`@tileflow/core`, official maps and their source assets live in `@tileflow/maps`, and React
-rendering lives in `@tileflow/react`.
-
-Docs: https://tileflow.dev/docs