Fixes from mapping public repos: scanner 0.10.0, Rules 4, lanes, Airflow demo, eval

Nine public repos were mapped with the skill; every fix is general, none names a framework
taken from them.

- Scanner 0.8–0.10: one rule for generated and vendored code; proto messages as classes and
  gRPC ends in every language; a queue needs a producer and a consumer in repo code; no
  false SQL writes or tables (statement shape, keyword stop-list, interpolated names); C#
  global usings; route handlers passed by reference or nested, same-file mounts composed,
  route keys normalised to {id}; calls through typed fields and interfaces two levels
  down, Go method sets, Python bases; Rust test code dropped; exclude: remembered; field
  visibility; a "Not scanned" section and deployable.unscanned.
- Rescans go full only when a deployable, module or the scanner changes; stale facts are
  found by line and say why; evidence moves with the code.
- Rules 4 (SKILL.md): secrets read as key names only, compose files included;
  .gitattributes written into the output directory; deployables, gateways and job queues
  worded generically; external.unused and the route warnings.
- Audit: budget counted in boxes, deterministic; --full-audit; lane checks (lane-drop,
  gap-stub, lane-gap) and lane names in text.over-line.
- Viewer: taps drop straight onto storage lanes again, as in 1.1.1.
- Demo: the features and forecast pipelines run on Airflow, not Flyte.
- Eval: scenarios 1–7 rerun (scenario 3 gains a secrets check); see eval/README.md.

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

Author: si1verwind17

README.md

@@ -60,8 +60,9 @@ Later, run it again, or ask:
 
 > Refresh the code map for the latest commit.
 
-The map lands in `docs/viz-code/`. Open `docs/viz-code/index.html`, and commit `code-map.json`, `stack.yaml` and
-`README.md` from that folder; the rest are working files, already gitignored.
+The map lands in `docs/viz-code/`, and nothing outside it is touched. Open `docs/viz-code/index.html`, and commit
+`code-map.json`, `stack.yaml`, `README.md`, `.gitignore` and `.gitattributes` from that folder; the rest are working
+files, already gitignored.
 
 **Found something it gets wrong?** Run the skill with `send-feedback`
 (`/codebase-map:visualizing-codebases send-feedback`), or ask your agent to send feedback on the code map. It drafts

demo/parking-city/.gitattributes

@@ -7,7 +7,7 @@ code-map viewer can be demonstrated and tested on
 something public, with every kind of factory element present at least once.
 
 Eleven runtime services (Scala 3 + ZIO 2 + tapir, and Python), two shared
-libraries, one Airflow project and two Flyte projects.
+libraries and three Airflow projects.
 
 ## How it is wired
 
@@ -20,7 +20,7 @@ libraries, one Airflow project and two Flyte projects.
   `FINES_API_URL`, `SMTP_HOST`, `SENSORCLOUD_WS_URL`, ...) or fixed vendor hosts.
 - One Postgres holds all tables (`sql/schema.sql` shows the owner of each);
   the analytics warehouse is BigQuery.
-- The Airflow project and the two Flyte projects are deployed by registration
+- The three Airflow projects are deployed by registration into one DAG bucket
   (`deploy/register.sh`, `jobs/README.md`, `forecast/README.md`,
   `features/README.md`).
 
@@ -40,8 +40,8 @@ libraries, one Airflow project and two Flyte projects.
 | `analytics-loader` | Python | `analytics_loader/` |
 | `reporting-api` | Python | `reporting_api/` |
 | `nightly-jobs` (Airflow) | Python | `jobs/` |
-| `demand-forecast` (Flyte) | Python | `forecast/` |
-| `feature-store` (Flyte) | Python | `features/` |
+| `demand-forecast` (Airflow) | Python | `forecast/` |
+| `feature-store` (Airflow) | Python | `features/` |
 
 Libraries: `common` (Scala: JDBC helper, Kafka producer, config; used by
 reservations, pricing, billing) and `common_py` (Python: Pub/Sub wrapper,
@@ -59,7 +59,7 @@ Redis cache helper, Twilio SMS client, SMTP mailer, DB connect).
 | Pull subscription | `analytics_loader/app/main.py` + `common_py/common_py/pubsub.py` `Puller.pull`; subscription `bay-status-analytics` |
 | Dead letters | `billing/.../DeadLetters.scala` produces to `reservation-events.dlq` when event handling fails (`ReservationEventsConsumer.scala`) |
 | Rail yard (busy batch destinations) | `jobs/dags/*.py`: 10 DAGs, 4 to BigQuery, 3 to Postgres, 2 to S3, 1 to billing; several run many times a day (`*/15`, hourly) |
-| Cross-project batch | `forecast/workflows.py` `reference_task` to `compute_zone_features` in `features/workflows.py` |
+| Cross-project batch | `forecast/demand_forecast.py` `TriggerDagRunOperator` to the `zone_features` DAG in `features/zone_features.py` |
 | Warehouse + lane (database) | Postgres tables `reservations`, `reservation_outbox`, `tariffs`, `zones`, `invoices`, `payments`, `bay_status`, `daily_revenue`, `zone_utilisation`, `demand_forecast` (`sql/schema.sql`); BigQuery `analytics.bay_events` and friends |
 | Own cache | `reservations/.../QuoteCache.scala` on `REDIS_URL`, read by nobody else |
 | Shared cache | `SHARED_CACHE_URL`: written by `occupancy` (`common_py/common_py/cache.py`), read by `pricing/.../SharedCache.scala` and `city_dashboard/app/main.py` |
@@ -68,7 +68,7 @@ Redis cache helper, Twilio SMS client, SMTP mailer, DB connect).
 | Inbound webhook | `payments_webhook/app/main.py` `POST /webhooks/stripe` |
 | Read-only service | `reporting_api/app/main.py`: only SELECTs on `reservations`, `invoices`, `bay_status` |
 | Libraries (parts racks) | `common/` (sbt module) and `common_py/` (package) |
-| Twin | `pipelines_shared/` registered into both Flyte projects, `deploy/register.sh` |
+| Twin | `pipelines_shared/` synced by both the `features` and the `forecast` registration, `deploy/register.sh` |
 | Replicas | `deploy.replicas` in `docker-compose.yml`: `notifier` 2, `enforcement-worker` 3 |
 | Deliberate smell | see below |
 

demo/parking-city/README.md

@@ -1,13 +1,14 @@
 #!/usr/bin/env bash
 # Registers the orchestrated projects. Runtime services are deployed from
 # docker-compose.yml; these three are deployed by registration.
+# All three share one Airflow DAG bucket, each project in its own folder.
 set -euo pipefail
 
 # Airflow project -> service "nightly-jobs"
-gsutil -m rsync -r -d jobs/dags "gs://${AIRFLOW_DAGS_BUCKET}/dags"
+gsutil -m rsync -r -d -x '^(features|forecast|pipelines_shared)/' jobs/dags "gs://${AIRFLOW_DAGS_BUCKET}/dags"
 
-# Flyte project "features" -> service "feature-store"
-pyflyte register --project features --domain production --image "${PIPELINE_IMAGE}" features pipelines_shared
+# Airflow project "features" -> service "feature-store"
+gsutil -m rsync -r -d features "gs://${AIRFLOW_DAGS_BUCKET}/dags/features" && gsutil -m rsync -r -d pipelines_shared "gs://${AIRFLOW_DAGS_BUCKET}/dags/pipelines_shared"
 
-# Flyte project "forecast" -> service "demand-forecast"
-pyflyte register --project forecast --domain production --image "${PIPELINE_IMAGE}" forecast pipelines_shared
+# Airflow project "forecast" -> service "demand-forecast"
+gsutil -m rsync -r -d forecast "gs://${AIRFLOW_DAGS_BUCKET}/dags/forecast" && gsutil -m rsync -r -d pipelines_shared "gs://${AIRFLOW_DAGS_BUCKET}/dags/pipelines_shared"

demo/parking-city/deploy/register.sh

@@ -2,7 +2,7 @@
 # are NOT started here: they are reached through the env keys below
 # (DB_HOST, REDIS_URL, SHARED_CACHE_URL, KAFKA_BROKERS, ...).
 #
-# The Airflow project (jobs/) and the Flyte projects (forecast/, features/)
+# The three Airflow projects (jobs/, forecast/, features/)
 # are deployed by registration, see deploy/register.sh.
 
 x-db: &db

demo/parking-city/docker-compose.yml

@@ -0,0 +1 @@
+code-map.json linguist-generated=true -diff

demo/parking-city/docs/viz-code/.gitattributes

@@ -10,6 +10,8 @@ How to read the map: the field guide at https://si1verwind17.github.io/codebase-
 | `stack.yaml` | libraries and route styles this repo uses that the scanner does not know built in | the agent; you may edit | yes |
 | `map-notes.md` | your standing notes on the map | you | yes |
 | `README.md` | this file | `assemble.py` | yes |
+| `.gitignore` | keeps the files not committed out of git | `assemble.py`; you may add lines | yes |
+| `.gitattributes` | marks `code-map.json` generated, so diffs fold it | `assemble.py`; you may add lines | yes |
 | `index.html` | the map viewer page | `assemble.py`, `view.py` | no |
 | `audit.md` | drawing and content checks, findings | `assemble.py`, `audit.py` | no |
 | `structure.json`, `summary.md` | the scanner's facts, and the digest the agent reads | `extract.py` | no |