@spatialbay/sdk

Target home for the framework-light map engine currently living at ../../src/sdk/ inside the SpatialBay app (core, map, ui, processing, plugins — mirrors GeoLibre's packages/* split, see ../../PRD.md §4 and §13). The end goal: SpatialBay becomes a thin UI shell that consumes this package, the same way it already consumes @geomotion/gm.

Status: scaffolded, not yet extracted

This package is a real, empty shell — package.json + entry point only. The actual code (MapController, layer-sync, usePanelsStore, FloatingPanel, DockPanel, useSdk(), project schema/types) is still in spatialbay/src/sdk/*, imported by the app via @/sdk/..., not yet moved here. Extraction is a separate, deliberate migration (update every import site, verify nothing regresses) — not done in the same pass that scaffolded this shell, to avoid a big-bang rewrite risk.

Plan

1. Move src/sdk/{core,map,ui,processing,plugins} here one module at a time, each as its own commit, updating the app's imports to @spatialbay/sdk as each module lands (mirrors how @geomotion/gm was carved out of src/gm/ — see PRD.md §14 for that precedent).
2. Once the surface is stable, add this to the root package.json's workspaces and wire local dev via npm link/workspace resolution.
3. Publish privately once a registry is chosen (see ../../.npmrc — currently a template; needs a real registry URL + auth token before this can publish).

Local dev today

Until the extraction happens, treat this package as documentation of intent, not a working import — the app should keep importing from @/sdk/* directly.