Maintainer Notes
Use this page as the maintainer handoff for where to add features, which seams are stable, and which areas should be refactored carefully.
Where to add new features
- Runtime behavior:
Assets/DialogGraphSystem/Scripts/Runtime/Core - Node data:
Assets/DialogGraphSystem/Scripts/Runtime/Models - UI:
Assets/DialogGraphSystem/Scripts/Runtime/UI - Editor tooling:
Assets/DialogGraphSystem/Scripts/Editor
Fragile areas
- graph save/load and sub-asset management
- GUID stability and link rebuilding
- Undo/Redo around graph structural edits
- hard-coded resource paths
- AI extension assumptions about graph JSON shape
Verification responsibilities
- Run graph-traversal and import/export regression tests when changing stored graph structure or interchange behavior.
- Preserve the product boundary: the AI Extension is included with DGS, while AI Providers is separate and required only for AI authoring.
- Follow the documented schema-upgrade procedure; verify project backup, upgrade report, reference integrity, and rollback checks.
- Preserve existing
Resources.Loadpaths or provide a deliberate migration with compatibility coverage.
Agent guidance and test ownership
The DGS package includes its coding-agent guide at Assets/DialogGraphSystem/SKILL.md. The separately distributed AI Providers package has its own guide at Assets/Beka Forge/AI Providers/SKILL.md; use the guide for the package you are changing. These files guide development tools and are not runtime setup steps.
Development test assemblies are maintained in the source workspace and excluded from customer archives. Run them from their owning source project rather than expecting the test suite in an installed package.