Add new vector pool storage types, not yet used

[Keavon]

No description provided.

[cubic-dev-ai]

2 issues found across 9 files

Confidence score: 5/5

• contour.rs: subpaths allocates a temporary Vec for every span just to inspect at most four references, adding avoidable overhead for large vectors. Inspect the fixed-index references directly.
• consts.rs: The rationale for the threshold doesn’t match the 0.5 accuracy passed to Kurbo. Clarify that it controls endpoint coalescing, or derive it from the actual offset precision.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="node-graph/libraries/vector-types/src/vector/contour.rs">

<violation number="1" location="node-graph/libraries/vector-types/src/vector/contour.rs:109">
P2: `subpaths` heap-allocates a temporary `Vec<u32>` for every span just to inspect at most four references. Large vectors therefore incur one allocation per segment; validate the fixed-index references directly or use stack storage instead.</violation>
</file>

<file name="node-graph/libraries/vector-types/src/vector/algorithms/consts.rs">

<violation number="1" location="node-graph/libraries/vector-types/src/vector/algorithms/consts.rs:11">
P3: This rationale does not match the configured offset accuracy: `offset_bezpath` passes `0.5` to Kurbo, not `1e-6`. Clarify that this is a tighter endpoint-coalescing threshold, or derive it from the actual offset precision.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>