@velinussage/locus-agent-skill 0.1.49 → 0.1.51

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@velinussage/locus-agent-skill",
-  "version": "0.1.49",
+  "version": "0.1.51",
   "description": "Install the general Locus agent skill, the media-to-market photo/video location workflow, the surrounding-area purchase workflow, and the property-tax protest workflow for free, x402-paid, and MPP/Tempo-paid property context.",
   "type": "module",
   "bin": {

package/skill/locus-agent-tools/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: locus-agent-tools
 preamble-tier: 1
-version: 1.76.0
+version: 1.78.0
 description: Use for cited US place records — starting from an address, county, or directly from 1-5 photos or a short video — including parcels, zoning, permits, flood, drought and water supply, regional market/living briefs, meetings, budgets, audits, county data series, changes over time, and dynamic MCP event polling or signed webhooks.
 triggers:
   - start property search from image
@@ -46,7 +46,7 @@ triggers:
   - real estate webhook notifications
 allowed-tools: Bash Read AskUserQuestion
 license: MIT
-contentHash: c99cf9faae66
+contentHash: 0318559b599b
 ---
 
 # Locus Agent Capabilities
@@ -233,6 +233,14 @@ npx agentcash@latest fetch https://api.locus.report/api/locus-flood-zone \
 
 Install the Locus skill separately with `npx @velinussage/locus-agent-skill@latest add`. Use the free Locus MCP or the `POST /api/<tool_name>` routes first.
 
+**GET fallback for POST-restricted agent sandboxes:** Sandboxed web-fetch environments that can only issue `GET` requests can call any read-only free tool via `GET https://api.locus.report/tools/call?name=<tool_name>&address=<url_encoded_address>` (or `&arguments=<url_encoded_json>`) and `GET https://api.locus.report/api/<free_tool_name>?address=<url_encoded_address>`. Write/participation tools (`locus_request_coverage`, `locus_agent_feedback`) and paid endpoints remain `POST`-only.
+
+**Community, subdivision, HOA/CC&R, age-restriction, and non-PII ownership structure (`/api/locus_subdivision_profile`, `/api/locus_hoa_context`, `/api/locus_age_restriction_context`, `locus_parcel_lookup`):**
+- `locus_parcel_lookup` exposes non-PII structural ownership and tenure fields derived from the county roll (`ownershipEntityClass: "individual_or_joint" | "trust_or_estate" | "llc_or_lp" | "corporation" | "hoa_or_common_area" | "government_or_nonprofit" | "unknown"`, `coOwnerPattern`, `deedInstrumentType`, `subdivisionName`, `lastTransferDate`, `yearsSinceLastTransfer`, and `tenureCohort`) without exposing natural-person owner names on free or stored replay artifacts. Recorded situs addresses are public land records in all 50 states (state Address Confidentiality Program statutes such as NC G.S. 15C-8(h) bar substitute addresses on recorded deeds), whereas off-site mailing street addresses are never republished (`mailingDiffersFromSitus: boolean` and 2-letter `mailingState` only).
+- `/api/locus_subdivision_profile` aggregates parcel-roll and polygon metrics across a recorded subdivision, PUD, or condo regime (unit/parcel count, ownership-class mix, absentee share, holding-period median and cohorts, year-built cohorts, assessed-value quartiles, and common-area parcels).
+- `/api/locus_hoa_context` returns 50-state + DC statutory common-interest community rules (declaration amendment thresholds/ceilings such as UCIOA/NC/TX/CO 67%, rental-cap grandfathering and floors such as FL § 720.306(1)(h) and CA Civ. Code §§ 4740–4741, covenant voting arithmetic for a given unit count, common-area HOA entities from the roll, keyless IRS Form 990 EO BMF nonprofit filings, and county Register of Deeds pointers).
+- `/api/locus_age_restriction_context` evaluates federal HOPA (`42 U.S.C. § 3607(b)(2)` / `24 CFR §§ 100.300–100.308`) and state 55+ housing registries/zoning overlays against tax-roll senior/homestead exemption flags, explicitly distinguishing legally age-restricted 55+/62+ communities from naturally occurring older demographics (NORCs such as Fearrington Village, NC).
+
 Read the live challenge and ask before every payment. Keep the settlement receipt.
 
 For broad requests, start with the current bundles in the top-agent manifest. For exact lanes, use the full catalog. A paid entry has a free underscore route only when it publishes `dualFreeTool` or a free `counterparts[]` entry. Paid-only atomics do not. Free executor names use underscores (`locus_zoning`); paid REST slugs use hyphens (`locus-zoning`). Execute the entry's exact `callName`.
@@ -645,9 +653,9 @@ These work for geocodable US addresses at no cost. Some accept address directly.
 | Mapped wetland overlap/proximity | `locus_wetland_context` | `{ "address": "...", "radiusMeters": 1500 }` | FWS NWI mapped-wetland overlap and nearby polygon evidence. Never a delineation, jurisdictional determination, parcel boundary, or permit decision. |
 | Dated LiDAR availability | `locus_3dep_availability` | `{ "address": "..." }` | National collection dates, USGS project metadata and NC state raster override. Catalog recency does not establish raster vintage. |
 | Elevation and sampled terrain | `locus_terrain_profile` | `{ "address": "..." }` or `{ "latitude": 35.22, "longitude": -80.84 }` | USGS EPQS/3DEP elevation plus sampled cardinal terrain profile/slopes. Never a survey, drainage, grading, or engineering conclusion. |
-| Physical site constraints composite | `locus_site_constraints` | `{ "address": "...", "radiusMeters": 250 }` or `{ "latitude": 35.72, "longitude": -79.18 }` | Unifies USGS terrain slope/relief, FEMA NFHL floodway/SFHA, USFWS NWI mapped wetlands, USDA SSURGO hydric/septic/shrink-swell/water-table/bedrock limits, Chatham County NC watershed/stream/river corridor buffers where applicable, and OpenStreetMap linear ROW corridors (`linearCorridors`: transmission/distribution lines, pipelines, railways, and telecom trunks with ODbL non-easement caveats). National baseline; not a wetland delineation, survey, easement search, perc test, or buildability determination. |
+| Physical site constraints composite | `locus_site_constraints` | `{ "address": "...", "radiusMeters": 250 }` or `{ "latitude": 35.72, "longitude": -79.18 }` | Unifies USGS terrain slope/relief, FEMA NFHL floodway/SFHA, USFWS NWI mapped wetlands, USDA SSURGO hydric/septic/shrink-swell/water-table/bedrock limits, Chatham County NC watershed/stream/river corridor buffers where applicable, OpenStreetMap linear ROW corridors (`linearCorridors`: transmission/distribution lines, pipelines, railways, and telecom trunks with ODbL non-easement caveats), US DOT/FHWA National Bridge Inventory structures (`nationalBridgesNearby`: clearances and load postings, never condition ratings), and FAA Special Use Airspace (`specialUseAirspace`: Prohibited `P` and Restricted `R` zones). National baseline; not a wetland delineation, survey, easement search, perc test, flight authorization, or buildability determination. |
 | LiDAR DEM drainage routing, cut/fill earthwork & multi-pad comparison | `locus_lidar_drainage_profile` | `{ "address": "...", "padHalfSizeFt": 75, "includeDeliverables": true }` | Fetches NC OneMap 3-ft LiDAR DEM03 GeoTIFF where covered or USGS 3DEP Float32 GeoTIFF/grid nationally, then runs Barnes (2014) Priority-Flood depression filling, D8 steepest-descent flow routing, upstream off-pad catchment walk, depression/low-spot extraction, least-squares guidance-plane earthwork (cut/fill cubic yards for tilted vs level pad), multi-pad candidate comparison (Center/East/North), and SSURGO + neighboring soil fallback, plus optional `drainageSvg` and interactive `reportHtml`. Planning-grade screen only, not a stamped civil design. |
-| Transportation-noise proximity facts | `locus_noise_proximity` | `{ "address": "..." }` or `{ "latitude": 35.22, "longitude": -80.84 }` | Straight-line proximity to public-use airports and mapped major-road/rail centerlines. No decibel estimate or quiet/loud/safe/unsafe label. |
+| Transportation-noise proximity facts | `locus_noise_proximity` | `{ "address": "..." }` or `{ "latitude": 35.22, "longitude": -80.84 }` | Straight-line proximity to public-use airports, mapped major-road/rail centerlines, and FAA Prohibited/Restricted Special Use Airspace (`specialUseAirspace`). No decibel estimate or quiet/loud/safe/unsafe label. |
 | Nearby places and amenities | `locus_nearby_places` | `{ "address": "...", "radiusMeters": 800 }` | OpenStreetMap nearby amenities/places with categories, distance, and OSM provenance. |
 | Nearest emergency services and utilities | `locus_public_utilities` | `{ "address": "...", "radiusMeters": 5000 }` | Nearest mapped OpenStreetMap fire station, hospital/clinic, police, fire hydrant, electric substation, and water tower with straight-line distances and counts. Hydrants/infrastructure are often unnamed and still reported. Mapped facility distances only, never a fire-protection rating, insurance determination, or safety verdict. |
 | County Medicare fee-for-service spending | `locus_medicare_spending` | `{ "address": "..." }` | Latest/prior CMS county aggregate: Original Medicare fee-for-service beneficiary count, actual and standardized per-capita payment, and standardized year-over-year change. Not a provider price, individual bill, premium, care-quality/access measure, health inference, score, or property signal. |
@@ -656,9 +664,9 @@ These work for geocodable US addresses at no cost. Some accept address directly.
 | Aggregate traffic-crash context | `locus_traffic_crash_context` | `{ "address": "...", "radiiMeters": [200, 500, 1000], "lookbackYears": 3 }` | Small-cell-suppressed police-reported crash counts by official severity and mode. Registry coverage: Chicago all-reported, Virginia reportable-threshold, North Carolina nonmotorist and K+A subsets kept separate, Pikes Peak region PPACG reportable-threshold records for 2020-2024, plus nationwide FARS fatal-only fallback. No raw rows, examples, exact points, party details, score, forecast, or place verdict. |
 | Landslide history + susceptibility context | `locus_landslide_context` | `{ "address": "...", "searchRadiusMeters": 1000 }` or `{ "latitude": 35.78, "longitude": -78.64 }` | USGS v3 bounded inventory point/polygon records plus a separately labeled exact source-native n10 90-meter cell where the active snapshot publishes one. Top-level `status` (`complete` \| `partial` \| `unavailable`), `partial`, `degradedComponents`, `historyState`, and `susceptibilityState` keep inventory no-match, model out-of-footprint, stale/unavailable snapshot, and source failure distinct. The 0–81 model value is not probability or parcel engineering. |
 | FEMA NFIP flood-insurance claims (county) | `locus_nfip_claims` | `{ "address": "..." }` or `{ "latitude": 25.76, "longitude": -80.19 }` | FEMA OpenFEMA NFIP redacted flood-insurance claims aggregated to the county: total claim count, total paid, year range, and top rated flood zones. Redacted (no address/PII), county-level historical fact, never a prediction or risk score. |
-| Historical wildfire perimeters | `locus_wildfire_history` | `{ "address": "..." }` or `{ "latitude": 38.6, "longitude": -122.5 }` | WFIGS interagency historical wildfire perimeters within about 5 miles: incident name, category, acres, discovery year. Realized-event records (complements the modeled `locus_wildfire_risk`); most non-Western points return none, an honest `out_of_coverage`. |
+| Historical and active wildfire perimeters | `locus_wildfire_history` | `{ "address": "..." }` or `{ "latitude": 38.6, "longitude": -122.5 }` | WFIGS interagency historical wildfire perimeters (~5 miles) plus current NIFC interagency perimeters (`activePerimeters` within ~10 miles: incident name, unique fire ID, acres, percent contained, discovery/current date, and currency-checked InciWeb link where matched). Realized-event records (complements the modeled `locus_wildfire_risk`); most non-Western points return none, an honest `out_of_coverage`. |
 | Soil context and site constraints | `locus_soil_context` | `{ "address": "..." }` or `{ "latitude": 35.9, "longitude": -78.9 }` | USDA NRCS SSURGO soil suitability at a point: NRCS engineering ratings (Very/Somewhat/Not limited, with limiting features) for dwellings, septic absorption fields, and shallow excavations, plus drainage, hydric, slope, shrink-swell (linear extensibility), taxonomic order, and farmland class. Soil-map-unit-level screening context for septic/foundation/drainage/buildability, never a geotechnical, perc-test, permit, or safe/unsafe/buildable verdict. Developed/urban points often return `out_of_coverage` (no soil component). |
-| Data-center or large-development watch prompts | `locus_data_center_watch` | `{ "address": "..." }` or `{ "state": "NC", "county": "Wake County", "municipality": "Raleigh" }` | Bounded official-source query pack and lead-discovery prompts for large projects, data centers, utility/water/planning sources. |
+| Data-center or large-development watch prompts | `locus_data_center_watch` | `{ "address": "..." }` or `{ "state": "NC", "county": "Wake County", "municipality": "Raleigh" }` | Bounded official-source query pack and lead-discovery prompts for large projects, data centers, utility/water/planning sources, plus deterministic `mappedOsmDataCenters` proximity (ODbL 1.0 crowd-mapped observation, non-official) when a coordinate or address is resolved. |
 | Local ordinance and storefront-process leads | `locus_ordinance_leads` | `{ "address": "...", "topics": ["occupancy", "fee_schedule", "signage", "sidewalk_cafe", "published_review_timeline"] }` or `{ "place": "Raleigh, NC", "liveSearch": true }` | Jurisdiction-locked first-party query pack, reviewed process pointers, and optional operator-enabled Gov-Index pointer discovery (`govIndex`). Numeric fees/timelines require an exact dated official source; published timelines are guidance, not predictions. Leads only, no restricted code body, not legal advice. |
 | Coastal county catalog | `locus_coastal_county_catalog` | `{}` or `{ "county": "new-hanover-nc" }` | Catalog of supported coastal source packs, overlays, source leads, and limitations. |
 

package/skill/locus-land-entitlement/SKILL.md

@@ -2,7 +2,7 @@
 name: locus-land-entitlement
 description: Use when a developer, land buyer, builder, or agent needs a pre-engineering land entitlement, rezoning, subdivision, physical site-constraint, LiDAR drainage/earthwork, or utility-reach screen for a US parcel or address from cited Locus records without turning public records into a go/no-go verdict.
 preamble-tier: 2
-version: 1.1.0
+version: 1.2.0
 triggers:
   - land entitlement
   - rezoning feasibility
@@ -63,6 +63,7 @@ Produce a cited, pre-engineering land entitlement and physical site-constraints
      - **Soils (`locus_soil_context`):** USDA SSURGO map unit, `hydricRating`, `drainageClass`, shrink-swell class, `annualMinimumWaterTableDepth`, `shallowestBedrockDepth`, and septic absorption field rating.
      - **Watershed & Stream Buffers:** in Chatham County, NC, report `Chatham_WPReferenceLayers` hits (Jordan Lake 50-ft buffers, perennial/intermittent stream buffers, 100-ft river corridor, USGS blue-line streams, and 2,500-ft public water hazard buffers).
      - **Linear ROW Corridors (`linearCorridors`):** OpenStreetMap Overpass screen (`power_transmission_or_distribution`, `pipeline`, `railway`, `telecom_trunk`) with `nearestByCategory`, `within100mCount`, and `within250mCount` (substations and point towers are excluded so linear ROW encroachments stay distinct from `locus_public_utilities`). Always state the ODbL caveat: mapped centerlines are crowd-sourced observations, not recorded easements or 811 locates.
+     - **Bridges & Special-Use Airspace (`nationalBridgesNearby`, `specialUseAirspace`):** US DOT/FHWA National Bridge Inventory structures near the parcel (vertical clearance and posted load status; condition ratings are never requested) plus FAA Prohibited (`P`) and Restricted (`R`) Special Use Airspace zones (altitude floor/ceiling, controlling agency, hours of use; informational only, not LAANC or flight authorization).
 5. **LiDAR DEM Drainage Routing, Cut/Fill Earthwork & Multi-Pad Comparison (free):**
    - Call `locus_lidar_drainage_profile` (`padHalfSizeFt: 75`, `includeDeliverables: true`).
    - Present the deterministic terrain findings: