@aqian0/dsh-unity 0.0.0-stage → 0.1.0

package/skills/implement-in-app-purchases/references/platform-notes.md

@@ -0,0 +1,55 @@
+# Unity IAP Platform-Specific Notes
+
+This file lists only the platform behavior agents commonly get wrong. For the extension APIs, setup steps and code samples, read the docs pages below before writing the code, and again if a step fails. Look up individual extension types in the package's `xrefmap.yml`. In API URLs, replace `<VERSION>` with the major.minor of `com.unity.purchasing` in `Packages/packages-lock.json`.
+
+- [Apple App Store](https://docs.unity.com/en-us/iap/apple-store.md): promotional purchases, Ask-to-Buy, offer code redemption, App Account Token and storefront.
+- [Use Google Play billing extensions](https://docs.unity.com/en-us/iap/use-google-play-billing-extensions.md): obfuscated IDs, subscription upgrade and downgrade, and deferred subscription changes.
+- [Receipt validation](https://docs.unity.com/en-us/iap/receipt-validation.md): Google local validation and Apple server-side validation.
+- [SubscriptionInfo class reference](https://docs.unity.com/en-us/iap/subscriptioninfo-class-reference.md): per-store behavior of each method.
+
+## Table of Contents
+
+- [Apple App Store](#apple-app-store)
+- [Google Play Store](#google-play-store)
+- [SubscriptionInfo platform differences](#subscriptioninfo-platform-differences)
+- [Cross-platform rules](#cross-platform-rules)
+
+## Apple App Store
+
+- If you subscribe to `AppleStoreExtendedPurchaseService.OnPromotionalPurchaseIntercepted`, you MUST eventually call `ContinuePromotionalPurchases()`, because otherwise the promotional purchase hangs indefinitely.
+- Ask-to-Buy purchases arrive through `store.OnPurchaseDeferred`. Show a "pending approval" state and don't grant content, because the purchase arrives later through `OnPurchasePending` if a parent approves it, or fails if they decline.
+- To test Ask-to-Buy in the sandbox, set `AppleStoreExtendedPurchaseService.simulateAskToBuy = true`. Remove it before release.
+- Handle `OnEntitlementRevoked` (for example after a refund) by removing the content. It receives the product ID as a `string`.
+- Check `AppleStoreExtendedService.canMakePayments` before showing a store, because parental controls can block payments.
+- Apple non-renewable subscriptions can't be restored through `RestoreTransactions`. Track them server-side.
+
+## Google Play Store
+
+- `UpgradeDowngradeSubscription` takes the player's current subscription `Order`, the new `Product`, and a `GooglePlayReplacementMode`. Read the [GooglePlayReplacementMode API](https://docs.unity3d.com/Packages/com.unity.purchasing@<VERSION>/api/UnityEngine.Purchasing.GooglePlayReplacementMode.html) page to pick the mode that matches the user's billing intent, and confirm the choice with the user, because each mode charges the player differently.
+- Pass hashed values to `SetObfuscatedAccountId` and `SetObfuscatedProfileId`, never raw user IDs, because Google rejects personally identifiable values.
+- `OnDeferredPaymentUntilRenewalDate` is on `GooglePlayStoreExtendedPurchaseService`, not on `StoreController`.
+
+## SubscriptionInfo platform differences
+
+| Method | Apple | Google |
+|---|---|---|
+| `GetPurchaseDate()` | Returns the **most recent renewal** date | Returns the **original purchase** date |
+| `GetCancelDate()` | Returns the cancellation date | Returns `DateTime.MinValue` (not supported) |
+
+Check `IsSubscribed()` first. A `Result.Unsupported` result means the platform doesn't provide that information.
+
+## Cross-platform rules
+
+- Platform extension services are `null` on other platforms and in the Editor:
+
+  | Extension | iOS | Android | Editor |
+  |---|---|---|---|
+  | `AppleStoreExtendedService` | Available | `null` | `null` |
+  | `AppleStoreExtendedPurchaseService` | Available | `null` | `null` |
+  | `GooglePlayStoreExtendedService` | `null` | Available | `null` |
+  | `GooglePlayStoreExtendedPurchaseService` | `null` | Available | `null` |
+
+  Null-check each one with `if` before use, because `?.` doesn't work with `+=`.
+- Add a "Restore Purchases" button on iOS that calls `store.RestoreTransactions()`, because Apple's review guidelines require it.
+- Check subscription status at every app launch, not only at purchase time, because subscriptions can expire or be cancelled outside the app.
+- Test with Apple sandbox accounts and Google license testing accounts, so test purchases aren't charged.

package/skills/implement-in-app-purchases/references/pre-check.md

@@ -0,0 +1,207 @@
+# Pre-Check: Project Scan and Path Routing
+
+Links to other reference files point to files in this `references/` folder. Any other relative paths resolve to the skill directory.
+
+## Table of Contents
+
+- [Ambiguous Intent](#ambiguous-intent)
+- [IAP D2C Capabilities (Direct-to-Customer, Third-Party Payment Provider)](#iap-d2c-capabilities-direct-to-customer-third-party-payment-provider)
+- [Scan Order (standard IAP paths)](#scan-order-standard-iap-paths)
+- [Routing Summary](#routing-summary)
+
+  Scan steps: [1 — Third-Party IAP Package Check](#1--third-party-iap-package-check-highest-priority) · [2 — Native Google Billing](#2--native-google-billing-check) · [2b — Native iOS StoreKit](#2b--native-ios-storekit-check) · [3 — Unity IAP v4](#3--unity-iap-v4-check) · [4 — Unity IAP v5 Already Installed](#4--unity-iap-v5-already-installed) · [5 — No IAP Detected](#5--no-iap-detected)
+  Third-party sub-checks: [1a Essential Kit](#1a--essential-kit-conversion-supported) · [1b UniPay](#1b--unipay-assessment-path) · [1c RevenueCat](#1c--revenuecat-assessment-path) · [1d Adapty](#1d--adapty-assessment-path)
+
+Run this scan before doing anything else. Do not read any other reference file or make any changes until routing is resolved.
+
+## Ambiguous Intent
+
+If the user's prompt does not clearly indicate which billing backend they want — for example:
+
+- "Add a StoreController for me"
+- "Add a purchase manager"
+- "Set up IAP"
+- "Help me add in-app purchases"
+- "Upgrade to latest IAP"
+
+**Stop and ask before scanning or routing:**
+
+> "Would you like to implement purchasing using:
+> - **Apple App Store / Google Play** (standard platform billing), or
+> - **IAP D2C Capabilities** (third-party payment provider such as Stripe or Coda via Unity Cloud)?"
+
+Do not assume a default. Route only after the user confirms their intent.
+
+---
+
+## IAP D2C Capabilities (Direct-to-Customer, Third-Party Payment Provider)
+
+If the user explicitly asks for IAP D2C Capabilities, Stripe/Coda payment integration, or a third-party payment provider, **do not follow the standard scan order below**. Instead:
+
+- If the project has IAP v4, native Google Billing, or a third-party IAP package → resolve those blockers first using the standard scan order, then return here.
+- If the project has no IAP, or has `com.unity.purchasing` **v5.4+** → route to [path-implement-iap-d2c.md](path-implement-iap-d2c.md).
+- If the project has `com.unity.purchasing` **v5.0–5.3** → inform the user that IAP D2C Capabilities require v5.4+, instruct them to upgrade via Package Manager, and continue once the upgrade is confirmed.
+
+---
+
+## Scan Order (standard IAP paths)
+
+Run scans in this exact order. The first match wins — stop scanning and route immediately.
+
+---
+
+### 1 — Third-Party IAP Package Check (highest priority)
+
+#### 1a — Essential Kit (conversion supported)
+
+Search `Packages/manifest.json` and `Packages/packages-lock.json` for `com.voxelbusters.essentialkit`.
+
+**If found → only one path is valid:**
+
+> Route to [convert-essentialkit.md](convert-essentialkit.md)
+
+Inform the user that Essential Kit was detected and that the conversion path will be used. Do not offer any other path.
+
+---
+
+#### 1b — UniPay (assessment path)
+
+Search `Packages/manifest.json`, `Packages/packages-lock.json`, and `Assets/Plugins/` for UniPay signals:
+
+```
+com\.flobuk\.unipay|UniPay|Assets/Plugins/UniPay|Assets/Plugins/SIS
+```
+
+**If found → only one path is valid:**
+
+> Route to [convert-unipay.md](convert-unipay.md)
+
+Inform the user that UniPay was detected and that the assessment path will be used. Do not offer any other path.
+
+---
+
+#### 1c — RevenueCat (assessment path)
+
+Search `Packages/manifest.json` and `Packages/packages-lock.json` for `com.revenuecat.purchases-unity`.
+
+**If found → only one path is valid:**
+
+> Route to [convert-revenuecat.md](convert-revenuecat.md)
+
+Inform the user that RevenueCat was detected and that the assessment path will be used. Do not offer any other path.
+
+---
+
+#### 1d — Adapty (assessment path)
+
+Search `Packages/manifest.json`, `Packages/packages-lock.json`, and `Assets/` for Adapty signals:
+
+```
+com\.adapty|Assets/Adapty|AdaptySDK
+```
+
+**If found → only one path is valid:**
+
+> Route to [convert-adapty.md](convert-adapty.md)
+
+Inform the user that Adapty was detected and that the assessment path will be used. Do not offer any other path.
+
+---
+
+### 2 — Native Google Billing Check
+
+Search the following locations:
+
+- `Assets/**/*.cs` for: `AndroidJavaObject|AndroidJavaClass|BillingClient|BillingManager|GoogleBilling|BillingBridge`
+- `Assets/Plugins/Android/**/*.java`, `*.kt` for: `com\.android\.billingclient`
+- `mainTemplate.gradle`, `launcherTemplate.gradle`, `baseProjectTemplate.gradle` for: `com\.android\.billingclient:billing`
+
+**If found → only one path is valid:**
+
+> Route to [path-convert-native-google-billing.md](path-convert-native-google-billing.md)
+
+Inform the user that native Google Billing was detected and that the conversion path will be used. If `com.unity.purchasing` is absent or not the latest stable version, instruct the user to install or upgrade to the latest stable version via Package Manager before proceeding.
+
+Do not offer any other path.
+
+---
+
+### 2b — Native iOS StoreKit Check
+
+Search the following for native StoreKit signals:
+
+- `Assets/Plugins/iOS/**/*.m`, `*.mm`, `*.h`, `*.swift` for: `SKProductsRequest|SKPaymentQueue|SKPaymentTransaction|SKPaymentTransactionObserver|Product\.products|Transaction\.currentEntitlements`
+- `Assets/**/*.cs` for: `DllImport.*__Internal` combined with IAP-related method names, or `UnitySendMessage` calls associated with StoreKit
+
+**If found → only one path is valid:**
+
+> Route to [path-convert-native-storekit.md](path-convert-native-storekit.md)
+
+Inform the user that a native iOS StoreKit plugin was detected and that the conversion path will be used. If `com.unity.purchasing` is absent or not the latest stable version, instruct the user to install or upgrade via Package Manager before proceeding.
+
+Do not offer any other path.
+
+---
+
+### 3 — Unity IAP v4 Check
+
+Search `Packages/manifest.json` for `com.unity.purchasing` with a version matching `4\.`.
+
+Also search `Assets/**/*.cs` for legacy v4 API patterns:
+
+```
+IStoreListener|UnityPurchasing\.Initialize|ConfigurationBuilder
+```
+
+**If found → only one path is valid:**
+
+> Route to [migration-v4-to-v5.md](migration-v4-to-v5.md)
+
+Inform the user that Unity IAP v4 was detected and that the v4→v5 migration path will be used. Do not offer any other path.
+
+---
+
+### 4 — Unity IAP v5 Already Installed
+
+If none of the above matched, search `Packages/manifest.json` for `com.unity.purchasing` with a version matching `5\.`:
+
+**If found → inform the user:**
+
+> "This project already has Unity IAP v5 installed. You can extend the existing setup — for example, add new products, add platform-specific features, or integrate IAP D2C Capabilities. What would you like to do?"
+
+Then route based on the user's answer. Do not automatically route to the new-project path — the project already has IAP configured.
+
+---
+
+### 5 — No IAP Detected
+
+If none of the above matched and `com.unity.purchasing` is absent from `manifest.json`:
+
+**→ only one path is valid:**
+
+> Route to [path-add-iap-to-new-project.md](path-add-iap-to-new-project.md)
+
+---
+
+## Routing Summary
+
+| What is detected | Valid path |
+|---|---|
+| Essential Kit (`com.voxelbusters.essentialkit`) | Convert Essential Kit billing → IAP 5 — see convert-essentialkit.md |
+| UniPay (FLOBUK) | Assessment — see convert-unipay.md |
+| RevenueCat | Assessment — see convert-revenuecat.md |
+| Adapty | Assessment — see convert-adapty.md |
+| Native Google BillingClient | Convert native Google Billing → IAP 5 — see path-convert-native-google-billing.md |
+| Native iOS StoreKit plugin (`SKPaymentQueue` / `DllImport("__Internal")`) | Convert native StoreKit → IAP 5 — see path-convert-native-storekit.md |
+| `com.unity.purchasing` v4 or v4 API patterns | Migrate IAP v4 → v5 |
+| `com.unity.purchasing` v5 already installed | Ask user what to extend — do not auto-route |
+| No IAP detected | Add Unity IAP 5 to new project |
+| User explicitly requests IAP D2C Capabilities / payment provider | See IAP D2C Capabilities section above |
+
+---
+
+## Also check: Codeless catalog presence
+
+Regardless of which route above wins, check whether `Assets/Resources/IAPProductCatalog.json` exists. This is the **Codeless IAP** catalog and is independent of the routing decision — but if it is present and `enableCodelessAutoInitialization` is true, adding a scripted `StoreController` creates a race condition with `CodelessIAPStoreListener`.
+
+Surface the catalog's presence and auto-init flag to the user before generating scripted IAP code. See [codeless-catalog.md](codeless-catalog.md) for the race condition details and the three mitigation options.

package/skills/implement-in-app-purchases/references/topic-map.md

@@ -0,0 +1,46 @@
+# Full topic map
+
+Before you go forward with a workflow or diagnosis:
+
+1. Open and read the [documentation page(s)](#full-topic-map) that cover the specific subject related to what you intend to do or fix and check if you've missed anything.
+2. Name the file(s) you read in your response.
+
+This is because your training knowledge about Unity might be out of date, incorrect, or for the wrong Unity version.
+
+Prefer `WebFetch` over `WebSearch` — faster and lands on the exact reference. Only fetch what you need.
+
+In docs.unity3d.com URLs, replace `<VERSION>` with the major.minor of `com.unity.purchasing` in `Packages/packages-lock.json` before fetching. The IAP manual pages on docs.unity.com aren't versioned, so use those URLs as written.
+
+- [Unity In-App Purchasing](https://docs.unity.com/en-us/iap.md): overview of the IAP manual and its sections.
+- [Initialize Unity IAP](https://docs.unity.com/en-us/iap/set-up-in-app-purchasing.md): install and initialize, with `StoreController` and D2C (`PaymentProvider.Name`, `RemoteCatalogProvider`) samples.
+- [Create your catalog programmatically](https://docs.unity.com/en-us/iap/code-catalog.md): define products with `CatalogProvider` and store-specific IDs.
+- [Purchases](https://docs.unity.com/en-us/iap/purchases.md): process pending purchases, confirm them, handle failed confirmations, and determine purchase status.
+- [Restore purchases](https://docs.unity.com/en-us/iap/restore-purchases.md): restore behavior on Google Play and Apple platforms.
+- [Receipt validation](https://docs.unity.com/en-us/iap/receipt-validation.md): local and server-side validation, and the receipt structure.
+- [SubscriptionInfo class reference](https://docs.unity.com/en-us/iap/subscriptioninfo-class-reference.md): every `SubscriptionInfo` method and its per-store behavior.
+- [Apple App Store](https://docs.unity.com/en-us/iap/apple-store.md): configure IAP for iOS, macOS and tvOS.
+- [Use Google Play billing extensions](https://docs.unity.com/en-us/iap/use-google-play-billing-extensions.md): obfuscated IDs and deferred subscription changes.
+- [Set up Codeless IAP](https://docs.unity.com/en-us/iap/codeless-iap.md): the IAP Catalog window, IAP buttons and automatic initialization.
+- [Upgrade from IAP v4 to v5](https://docs.unity.com/en-us/iap/upgrade-to-iap-v5.md): the official v4 to v5 API mapping.
+- [Integrate D2C payment providers workflow](https://docs.unity.com/en-us/iap/payment-providers/workflow.md): the D2C setup workflow for Stripe and Coda.
+- [Initiate a purchase](https://docs.unity.com/en-us/iap/payment-providers/initiate-purchase.md): D2C eligibility checks and the Purchase Options UI.
+- [Deep link success URL example](https://docs.unity.com/en-us/iap/payment-providers/success-deep-link.md): redirect players back to the app after D2C checkout.
+- [Test mode for D2C payments](https://docs.unity.com/en-us/iap/payment-providers/test-mode.md): simulate D2C purchases before a provider account is connected.
+- [Comply with Apple and Google external purchase requirements](https://docs.unity.com/en-us/iap/payment-providers/external-purchase-compliance.md): compliance checks, checkout URLs and transaction tokens.
+- [Add a routing rule](https://docs.unity.com/en-us/iap/payment-providers/routing.md): choose which payment providers players see.
+- [Create your Remote Catalog](https://docs.unity.com/en-us/iap/payment-providers/configure-remote-catalog.md): `.ucat` and `.catalog.csv` catalog items and deployment.
+
+## API reference
+
+The API is `UnityEngine.Purchasing`, part of the `com.unity.purchasing` package. It is versioned by package version, not Unity version, so check the project's installed package version before relying on a specific class or method.
+
+1. Use the `unity-cli` skill to check the installed package version.
+2. Fetch and cache `https://docs.unity3d.com/Packages/com.unity.purchasing@<VERSION>/xrefmap.yml`, replacing `<VERSION>` with the installed package's major.minor. This file maps every public API member's fully qualified name to its docs page `href`. Append the `href` to the same base URL, so `href: api/UnityEngine.Purchasing.StoreController.html` becomes `https://docs.unity3d.com/Packages/com.unity.purchasing@<VERSION>/api/UnityEngine.Purchasing.StoreController.html`.
+3. Grep the yml file locally for a class or method instead of refetching per lookup. Don't read the whole file.
+
+Always fetch the version matching the installed package rather than relying on training knowledge, since APIs are frequently marked obsolete between major versions (e.g. the v4 `UnityPurchasing` class is obsolete in v5).
+
+Most-used pages:
+
+- [StoreController API](https://docs.unity3d.com/Packages/com.unity.purchasing@<VERSION>/api/UnityEngine.Purchasing.StoreController.html): every `StoreController` method, event and property, with signatures.
+- [EntitlementStatus API](https://docs.unity3d.com/Packages/com.unity.purchasing@<VERSION>/api/UnityEngine.Purchasing.EntitlementStatus.html): the entitlement status values.

package/skills/initialize-ai-navigation/SKILL.md

@@ -0,0 +1,109 @@
+---
+name: initialize-ai-navigation
+description: Sets up and configures Unity AI Navigation, including NavMesh surfaces, agents, obstacles, and links. Use when the user asks about navigation meshes, pathfinding, patrol routes, or obstacle avoidance.
+---
+
+Determine what the user needs and guide them through navigation setup. See [navigation-system.md](references/navigation-system.md) for expanded component details, API notes, code recipes, and troubleshooting.
+
+## Important
+
+- Use the unity cli (`unity command --format json`) and the `unity-cli` and `unity-pipeline` skills for each step.
+- Before making changes, establish a baseline of the current behavior so you can tell whether a later result is actually caused by your change.
+- Create a restore point you can roll back to if your changes fail.
+- Do only what's asked. Don't change unrelated assets or files.
+- Never leave verification code in the user's script. Never build logging or detection they didn't ask for. See [Final step](#final-step).
+- Avoid long explanations.
+
+## Full topic map
+
+Documentation pages and API entry points: [references/topic-map.md](references/topic-map.md).
+## Routing Logic
+
+| User Says | Interpretation |
+|-----------|---------------|
+| "add navigation" / "set up nav" | Full setup: NavMeshSurface + bake + NavMeshAgent |
+| "make this character navigate" | Add NavMeshAgent, ensure NavMesh exists |
+| "add pathfinding" | NavMeshAgent + movement script |
+| "agent won't move" / "path not found" | Troubleshoot — see Troubleshooting Decision Tree in reference |
+| "avoid obstacles" | NavMeshObstacle with carving or avoidance |
+| "connect two areas" / "jump across" | NavMeshLink between areas |
+| "patrol between points" | NavMeshAgent + patrol script |
+| "click to move" | NavMeshAgent + raycast click-to-move script |
+| "animate the character while navigating" | Couple Animator with NavMeshAgent |
+| "different agent sizes" | Configure agent types in Navigation window |
+| "areas and costs" / "restrict areas" | NavMesh area types, modifiers, and agent area masks |
+
+## Workflow
+
+### 0. Package Installation Check
+Before doing anything else, verify that `com.unity.ai.navigation` is installed. If it's missing,
+add it to `Packages/manifest.json` under `dependencies` — Unity resolves it when the Editor next
+regains focus, and this needs no Editor connection:
+
+```json
+"com.unity.ai.navigation": "<current 2.x version>"
+```
+
+Don't invent the version string, and don't copy another package's version, because package
+versions are independent. You must read the latest 2.x version from the Unity registry:
+`https://packages.unity.com/com.unity.ai.navigation` lists every published version. Use version 2.0.16 when in doubt.
+
+Proceed only once it's confirmed installed. If you have a live Editor to run C# in, see
+[navigation-system.md](references/navigation-system.md) for the `Client.Add` equivalent.
+
+### 1. Pre-Flight: Assess Current Navigation Setup
+Before making changes, inspect what already exists:
+1. Find the existing navigation components. With a connected Editor, query the live scene for
+   `NavMeshSurface`, `NavMeshAgent`, `NavMeshObstacle`, `NavMeshLink` and `NavMeshModifier` — see
+   the `unity-cli` skill for driving a running Editor. Without one, search the scene and prefab
+   files for those component names.
+2. List the configured agent types. With a connected Editor, loop over
+   `UnityEngine.AI.NavMesh.GetSettingsCount()` and `GetSettingsByIndex(i)`, and name each with
+   `GetSettingsNameFromID(settings.agentTypeID)`. Without one, read the `m_SettingNames` section in `ProjectSettings/NavMeshAreas.asset`.
+3. Summarize ALL detected navigation components before proposing changes.
+
+### 2. Gather Missing Information
+Before creating components, ensure the user has specified: walkable surfaces, agent type/size, agent behavior, obstacles, links, and area/cost requirements. Ask if anything is unclear. See the Information Gathering Checklist in the reference for full details.
+
+### 3. Planning & Execution
+Follow this general order. See the Component Setup Guide in the reference for detailed step-by-step instructions per component:
+1. **NavMesh Surface** — create the walkable mesh (bake it)
+2. **NavMesh Agent** — add pathfinding characters
+3. **NavMesh Obstacle** — add dynamic obstacles
+4. **NavMesh Link** — connect disconnected NavMesh areas
+5. **NavMesh Modifier / Modifier Volume** — fine-tune area types
+6. **Scripts** — movement, patrol, click-to-move, animation coupling (see Common Recipes in reference)
+
+### 4. Validation
+After setup, read these values with `eval` (fully qualified) rather than checking the Scene view by eye, because a NavMesh that looks right can still be missing or mismatched:
+
+1. Each `NavMeshSurface` has baked data: `navMeshData` isn't null.
+2. Each `NavMeshSurface.agentTypeID` matches the `NavMeshAgent.agentTypeID` of the agents that walk on it.
+3. Each agent can reach its destination: `agent.CalculatePath` to the target returns `true`, and the path's `status` is `PathComplete`. Use `NavMesh.CalculatePath(Vector3, Vector3, NavMeshQueryFilter, NavMeshPath)` if you check paths when a NavMeshAgent is not available.
+4. `NavMeshObstacle.carving` is on for NavMeshObstacle components that stay still in the scene or are expected to move slowly, and off for those expected to move fast.
+5. Each `NavMeshLink` has `activated` set to `true`, and `NavMesh.SamplePosition` finds the NavMesh within a short distance of both ends.
+6. Each agent's `areaMask` includes every area it must cross.
+7. No conflicting components (see Mixing Components Guide in reference).
+8. If a NavMeshAgent's GameObject has a Rigidbody, `isKinematic` is `true`.
+
+If a check fails, fix it and run the checks again before the Final step.
+
+## Final step
+
+Do the following checks:
+
+1. Check the project has zero console errors. Use `console_status` for counts.
+2. Stop there unless the user asked you to prove it works or you suspect a specific fault.
+3. If you do enter Play mode, do it once only to chase a fault you already suspect. Read the world through `eval` rather than adding logging, for example each agent's `pathStatus` and `remainingDistance` to see whether it reaches its destination. Take no screenshots as they take too much time.
+
+If a check fails, go back and reread the [docs pages](#full-topic-map) to find out what you missed.
+
+## Final report
+
+Summarize what was created or changed:
+- NavMesh Surfaces: which GameObject, agent type, geometry mode, bake status
+- NavMesh Agent(s): which GameObject, speed, stopping distance, area mask
+- NavMesh Obstacle(s): which GameObject, shape, carve on/off
+- NavMesh Link(s): start/end, bidirectional, area type
+- Scripts: which scripts attached to which GameObjects
+- Any manual steps required (adjust waypoints, re-bake after scene changes, etc.)