chore: fix 'architots' → 'architools' typo in gis-api-client comments + plan 005

No code/contract change — comments and docs only.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/plans/005-gis-api-export-endpoints.md

@@ -71,7 +71,7 @@ type Signer = {
 };
 ```
 
-gis-api never resolves signers — architots picks them client-side
+gis-api never resolves signers — architools picks them client-side
 (merged DB rows + ENV defaults) and sends the final string-only struct
 in the request body. gis-api renders verbatim into the PDF footer /
 PIZ cartouche. Co-signer rendering follows the same shape.
@@ -113,7 +113,7 @@ peste 400 m), parcela conturată cu roșu peste fundal satelit / orto.
 
 - Drop `getEffectiveSession` → use gis-api's bearer-token + claims context.
 - Drop `prisma.eterraUser.findUnique` → use the signer struct from body.
-- Drop `resolveSignerIdentity` → trust body.signer (architots-side validated).
+- Drop `resolveSignerIdentity` → trust body.signer (architools-side validated).
 - Drop `trackUsage` → optional; can keep a thin audit row in gis_meta if
   desired, but skip credit accounting.
 - `enrichFeatureIfNeeded` → call the existing
@@ -230,7 +230,7 @@ Stereo70.
 ### Replace in port
 
 - Strip the `geojson` + `gpkg` branches — gis-api endpoint is DXF-only
-  (architots GeoJSON export already exists via the gis-api search path,
+  (architools GeoJSON export already exists via the gis-api search path,
   and GPKG is rarely useful for single-parcel workflows).
 - The neighbor query is similar to PAD's — share the helper.
 
@@ -292,7 +292,7 @@ consumă credit ePay). Streams the eTerra response directly.
 
 Architots already speaks all five via the thin client
 (`gisApi.exports.{piz,pad,coordsXlsx,dxf,cfIntern}` in
-`src/lib/gis-api-client.ts`). No architots change required as each
+`src/lib/gis-api-client.ts`). No architools change required as each
 gis-api endpoint ships.
 
 ---
@@ -302,7 +302,7 @@ gis-api endpoint ships.
 After each ships:
 
 ```bash
-# From architots cwd, on the live deploy (assumes test cad 354686 in UAT Cluj-Napoca, siruta 54975):
+# From architools cwd, on the live deploy (assumes test cad 354686 in UAT Cluj-Napoca, siruta 54975):
 # (Replace <PARCEL_UUID> with the GisFeature uuid for that cadref.)
 
 # Coord
@@ -339,8 +339,8 @@ to confirm rendering parity with eterra.live's output.
 
 ## Related memory
 
-- [[architots-cutover-state-2026-05-20]] — V2 panel state
+- [[architools-cutover-state-2026-05-20]] — V2 panel state
 - [[v2-panel-contract]] — panel section layout
 - [[parcel-enrich-contract]] — gis-api /parcel/enrich auto vs manual
 - [[gis-api-parcela-by-ref]] — find chain endpoint
-- [[architots-auto-deploy-webhook]] — push → live in ~90s
+- [[architools-auto-deploy-webhook]] — push → live in ~90s

src/lib/gis-api-client.ts

@@ -413,12 +413,12 @@ export const gisApi = {
 
   // ── Exports (geoportal V2 panel toolbar) ─────────────────────────
   // All four endpoints return binary bodies (PDF / XLSX / DXF) — proxy
-  // them through rawResponse so the architots route handler can stream
+  // them through rawResponse so the architools route handler can stream
   // straight to the browser without re-encoding.
   //
   // Contract documented in docs/plans/005-gis-api-export-endpoints.md.
   // Implementation pending in gis-api session — until shipped, each call
-  // here will get a 404 from gis-api, which architots routes surface
+  // here will get a 404 from gis-api, which architools routes surface
   // as a friendly "Această funcție urmează" message.
   exports: {
     piz: (