Ship production navigation authoring workflow

This commit is contained in:
Rbanh committed 2026-07-12 02:53:43 -04:00
1 parent 0798aa5d57
commit b4aa61e394
35 files changed
+3898 -602

No files matched your search

@@ -6,8 +6,9 @@ This is the navigation production loop required by the M7 content-production mil
## Status
Architecture and dependency compatibility are established. Implementation and production
acceptance are in progress.
Architecture, dependency compatibility, composed-source resolution, persisted path samples,
corrective source-level QA, and live debug-editor acceptance are complete. Packaged/release
acceptance remains explicitly deferred until the project owner requests another packaged pass.
## Outcome
@@ -18,13 +19,15 @@ use the same artifact through a game-owned runtime query API and headless releas
## Architecture
- Shared reflected components own bounds, obstacles, area volumes, links, and scene bake settings.
- The scene crate owns deterministic source fingerprinting, bake artifact IO, and validation.
- The scene crate owns deterministic composed-source resolution, source fingerprinting, bake
artifact IO, the engine-independent query core, and validation.
- Rerecast performs the 3D walkable-surface bake without coupling navigation to a Bevy plugin
release. Polyanya performs proven any-angle runtime and editor-preview path queries.
- Overlapping primitive and additive-brush triangles enter the deterministic bake source; distant
geometry and navigation authoring are excluded from each bounds fingerprint.
- The game crate owns loading and querying baked artifacts. Editor UI calls that public API for
preview rather than implementing a second pathfinder.
geometry and navigation authoring are excluded from each bounds fingerprint. No synthetic bounds
floor is added.
- The game crate adapts the shared query core to Bevy types and exposes renderer-free artifact
validation. Editor preview and project validation do not implement separate pathfinders.
- Generated artifacts live under `assets/navigation/generated/`, are project-relative runtime
dependencies, and never serialize viewport helpers into authored scenes.
@@ -39,8 +42,8 @@ use the same artifact through a game-owned runtime query API and headless releas
preview.
5. Add owner-attributed project validation for invalid links, missing/stale artifacts, unreachable
preview samples, and bake failures.
6. Commit a small sample scene/artifact and run automated, headless, live editor, PIE, and packaged
runtime acceptance.
6. Commit a small sample scene/artifact and run automated, headless, and live debug-editor
acceptance. PIE and packaged runtime acceptance remain deferred by project-owner direction.
## Acceptance Gates
@@ -55,6 +58,8 @@ use the same artifact through a game-owned runtime query API and headless releas
- Helper meshes, lines, endpoints, and bake state are transient and never serialize.
- Headless bake and project validation pass for the committed sample fixture, and package dependency
collection includes the current artifact.
- Visible subscenes and nested prefab contributors resolve identically from editor snapshots and
headless tooling; unsupported structural overrides block with an apply/unpack repair action.
## Deliberate Boundaries