@scoutflo/topology-contracts 0.11.0-flat.4 → 0.12.0-flat.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (12) hide show
  1. package/README.md +13 -13
  2. package/dist/src/investigation/context.d.ts +10405 -20303
  3. package/dist/src/investigation/context.js +30 -136
  4. package/dist/src/investigation/context.js.map +1 -1
  5. package/dist/src/investigation/flat.d.ts +202 -202
  6. package/dist/src/provenance/runtimeContainer.d.ts +4 -4
  7. package/dist/src/schemas/index.d.ts +1 -1
  8. package/dist/src/schemas/index.js +3 -11
  9. package/dist/src/schemas/index.js.map +1 -1
  10. package/dist/test/investigation-context.test.js +78 -426
  11. package/dist/test/investigation-context.test.js.map +1 -1
  12. package/package.json +1 -1
package/README.md CHANGED
@@ -16,19 +16,19 @@ This package owns:
16
16
 
17
17
  ## Gateway alert topology context
18
18
 
19
- `topologySlice` is the canonical topology reconstruction whenever it is present. When it is absent,
20
- legacy projections remain the compatibility fallback. The legacy
21
- `investigationContext.investigationResources` and `investigationContext.relatedServices` fields
22
- remain parseable for compatibility, but are deprecated derived projections and must not override
23
- or be merged back into `topologySlice`. Parsed legacy v1 payloads receive explicit `compatibility`
24
- metadata expressing that rule.
25
-
26
- All context input passes an iterative preflight before recursive parsing: maximum depth 12, maximum
27
- 1,000 object/array nodes, maximum 1 MiB aggregate key/string content, and bounded map keys. Opaque
28
- legacy records remain extensible only inside that aggregate budget.
29
-
30
- For untrusted recursive input, use `gatewayTopologyContextSchema` or
31
- `nestedTopologyResponseSchema`. Recursive node/child builders are intentionally not exported.
19
+ `topology.gateway-context.v2` carries a bounded `flatTopology` response, initialization,
20
+ connection hints and diagnostics. `flatTopology` is the only troubleshooting topology
21
+ representation; the nested slice, legacy investigation projection and compatibility fallback
22
+ are removed. A populated bootstrap requires a snapshot and matching selected/primary anchors.
23
+ Unavailable topology is explicit (`flatTopology: null`, `topologyAvailable: false`).
24
+
25
+ The flat read retains its own 1 MiB/4,000-container bound. The enclosing context has a
26
+ 1.25 MiB/4,500-container budget (depth 16) for the graph plus bounded correlation and
27
+ provenance diagnostics. Input is checked before schema traversal. The shared
28
+ The retired nested response schemas are removed. Candidate evidence validation remains available as `topologyCandidateEvidenceSchema`.
29
+
30
+ Upgrade Gateway and Voyager together with the matching alert-correlation package. Old v1
31
+ contexts are rejected rather than interpreted as a compatibility fallback.
32
32
 
33
33
  `candidateTargets` is a read-only transport projection of the authoritative
34
34
  `alertCorrelationCandidate`, not a second authoring model. It retains `displayName` for existing