fix(migration-to-aws): Resolve 3 remaining reviewer issues

1. Fix depth calculation algorithm direction (depth-calculation.md)
   - Previous: Algorithm processed R's dependencies (backwards)
   - Fixed: Now correctly processes resources that depend on R
   - Result: Dependent resources get higher depths (deploy later)

2. Resolve google_compute_network classification contradiction
   - Previous: Listed as PRIMARY in classification-rules.md
   - But: Shown as SECONDARY in output-schema.md example
   - And: Clustering Rule 1 treats networks specially
   - Fixed: Move google_compute_network to SECONDARY / network_path
   - Reason: Networks are infrastructure, not workloads

3. Fix remaining cluster ID format inconsistency (design.md)
   - Previous: Still used old format "web-app-us-central1"
   - Fixed: Updated to new format "compute_instance_us-central1_001"
   - Aligns with: clustering-algorithm.md Rule 6 specification

All reviewer feedback now fully addressed. Build passes all checks.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Author: icarthick

plugins/migration-to-aws/skills/gcp-to-aws/references/clustering/terraform/classification-rules.md

@@ -17,7 +17,6 @@ These resource types are always PRIMARY:
 - `google_redis_instance` — In-memory cache
 - `google_pubsub_topic` — Message queue
 - `google_dns_managed_zone` — DNS zone
-- `google_compute_network` — Virtual network
 - `google_monitoring_alert_policy` — Alert rule
 - `google_project_service` — API service enablement
 - `module.*` — Terraform module (treated as primary container)
@@ -39,6 +38,7 @@ Match resource type against secondary classification table. Each match assigns a
 
 ### Network Path (`network_path`)
 
+- `google_compute_network` — Virtual network (VPC)
 - `google_vpc_access_connector` — VPC connector for serverless
 - `google_compute_subnetwork` — Subnet
 - `google_compute_firewall` — Firewall rule

plugins/migration-to-aws/skills/gcp-to-aws/references/clustering/terraform/depth-calculation.md

@@ -39,11 +39,13 @@ Assign: `depth[resource] = 0` for all queued resources.
 While queue not empty:
 
 1. **Dequeue** resource R
-2. **For each** resource D in R's `dependencies[]`:
+2. **For each** resource D that depends on R (traverse reverse edges):
    - Update: `depth[D] = max(depth[D], depth[R] + 1)`
    - Decrement: `in_degree[D] -= 1`
    - **If** `in_degree[D]` becomes 0: **Enqueue** D
 
+**Note:** "Resources that depend on R" means all resources X where X's `dependencies[]` contains R. This correctly assigns higher depths to dependent resources (which must deploy later).
+
 ### Step 4: Cycle Detection
 
 If queue empties but unassigned resources remain:

plugins/migration-to-aws/skills/gcp-to-aws/references/phases/design.md

@@ -63,7 +63,7 @@ For each SECONDARY resource:
 {
   "clusters": [
     {
-      "cluster_id": "web-app-us-central1",
+      "cluster_id": "compute_instance_us-central1_001",
       "gcp_region": "us-central1",
       "aws_region": "us-east-1",
       "resources": [