docs(roadmap): add idea for auto-TRZ creation on object spawn

[FullGas1]

Summary

• Adds a roadmap idea: a config setting that automates createTroopZoneAtObject (FEAT-TROOP-ZONE-SCRIPTED-API, PR feat(zones): scripted API to add a pickup TRZ on any named object #129) so a TRZ_ is created automatically when a matching object (FOB, FARP, etc.) spawns, instead of an explicit scripted call per object.
• Not formalized into a lot — open questions (trigger event, selection criteria, generated TRZ_ naming, F10 menu refresh overlap) listed for a future grill-with-docs session.

Test plan

• Docs-only change, no code/tests affected.

Summary by Sourcery

Document a future configuration-driven option to create troop zones automatically for matching spawned objects.

Enhancements:

• Document a roadmap idea for automatically creating TRZ_ zones when matching mission objects spawn, building on the existing scripted troop-zone API.
• Capture the open design questions around spawn detection, object selection, generated zone naming, and F10 menu refresh behavior for future refinement.

Documentation:

• Add a roadmap entry describing automated troop-zone creation for spawned FOBs, FARPs, and similar objects.

[sourcery-ai]

Reviewer's Guide

Adds a non-formalized roadmap idea for configuration-driven automatic TRZ_ creation when matching FOBs, FARPs, or other objects appear, while recording the trigger, selection, naming, and menu-refresh questions that must be resolved before turning it into a PRD.

Sequence diagram for automatic TRZ creation on object spawn

sequenceDiagram
    participant Object as SpawnedObject
    participant CTLD as CTLDZoneManager
    participant TRZ as TRZ_
    participant F10 as F10Menu

    Object->>CTLD: [matching object appears]
    CTLD->>CTLD: createTroopZoneAtObject(objectName, trzName)
    CTLD->>TRZ: Create zone from object
    CTLD->>F10: [refresh behavior unresolved]

Loading

File-Level Changes

Change	Details	Files
Documents a roadmap proposal to automatically create a TRZ_ when a matching DCS object spawns, building on the existing scripted object-based API.	Describes a configuration-driven alternative to explicit per-object createTroopZoneAtObject calls. Defines candidate spawn triggers and object-selection rules for future investigation. Identifies generated TRZ_ naming, default metadata, and F10 menu refresh as unresolved design questions. Links the proposal to related roadmap precedents and existing dynamic-zone behavior.	dev/roadmap.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="dev/roadmap.md" line_range="228" />
<code_context>
+
+## TRZ_ automatique — création liée au spawn d'un objet (FOB, FARP, etc.)
+
+Demandé le 2026-08-26. `CTLDZoneManager:createTroopZoneAtObject(objectName, trzName)`
+(`FEAT-TROOP-ZONE-SCRIPTED-API`, PR #129) permet déjà de créer une `TRZ_` sur n'importe quel objet
+DCS nommé après coup, mais uniquement via un appel scripté explicite — un MM ou une intégration
+externe (ex. VMCT) doit le déclencher lui-même, objet par objet.
</code_context>
<issue_to_address>
**nitpick:** La formulation affirme que `createTroopZoneAtObject` fonctionne sur n'importe quel objet DCS nommé, alors que l'implémentation ne résout que les zones de trigger, unités, statiques, groupes et airbases/FARP. Un futur utilisateur qui cible un autre type d'objet obtient `false` et aucune TRZ.

**Triggers:** Lorsqu'un mission maker cible un objet DCS hors des cinq catégories actuellement prises en charge.

**Suggested fix:** Remplacer « n'importe quel objet DCS nommé » par la liste explicite des types supportés, ou préciser que l'API ne couvre que les objets résolus par son helper actuel.

```suggestion
(`FEAT-TROOP-ZONE-SCRIPTED-API`, PR #129) permet déjà de créer une `TRZ_` sur un objet DCS nommé de type zone de trigger, unité, statique, groupe ou airbase/FARP
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

nitpick: La formulation affirme que createTroopZoneAtObject fonctionne sur n'importe quel objet DCS nommé, alors que l'implémentation ne résout que les zones de trigger, unités, statiques, groupes et airbases/FARP. Un futur utilisateur qui cible un autre type d'objet obtient false et aucune TRZ.

Triggers: Lorsqu'un mission maker cible un objet DCS hors des cinq catégories actuellement prises en charge.

Suggested fix: Remplacer « n'importe quel objet DCS nommé » par la liste explicite des types supportés, ou préciser que l'API ne couvre que les objets résolus par son helper actuel.

Suggested change

	(`FEAT-TROOP-ZONE-SCRIPTED-API`, PR #129) permet déjà de créer une `TRZ_` sur n'importe quel objet
	(`FEAT-TROOP-ZONE-SCRIPTED-API`, PR #129) permet déjà de créer une `TRZ_` sur un objet DCS nommé de type zone de trigger, unité, statique, groupe ou airbase/FARP