Hidden SVG paths and groups still become painted BRep geometry

At v0.0.10 (81a79bc3665a4fedab02d3a8e273b9ac5d1af906), getSvgBRepShapes includes path geometry hidden with display or visibility. This can turn a hidden editor layer into visible output geometry.

Minimal reproduction (Bun from repository root):

import { identity } from "transformation-matrix"
import { getSvgBRepShapes } from "./lib/svg-to-brep-shapes"
const svg = `<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 10 10">
  <g display="none"><path d="M1 1 H9 V9 H1 Z"/></g>
</svg>`
console.log(getSvgBRepShapes({ svg, width: 10, height: 10, transform: identity() }).length)
// 1; expected 0 for the painted output

I also compared the following complete 10-by-10 SVGs using the installed @napi-rs/canvas SVG loader, drawing onto a transparent canvas and checking center pixel alpha:

The SVG rendering model excludes a display:none subtree from rendering; visibility:hidden suppresses painting. A fix should resolve display and effective visibility before emitting painted BRep shapes. The semantics differ: visibility is inherited and a descendant can override it, whereas a descendant cannot restore rendering inside a display:none subtree.

This does not use defs/symbols or multiple nested rings. I separately reproduced the hidden-group result against the local #32 implementation that skips definition subtrees, so it is distinct from #31/#32. The current regex-based path collection on main does not inspect these style attributes or ancestor state.

The five table cases were executed locally. Native renderer behavior for visibility inheritance overrides was not used as an oracle; such cases need specification-based regression coverage. Prepared with Codex (Astra) assistance.

Start in lib/svg-to-brep-shapes and reproduce the Bun example from the issue, then inspect the current regex-based path collection. Ensure display="none" subtrees and hidden visibility states do not emit painted BRep shapes while descendant visibility overrides follow SVG inheritance rules; add regression coverage for the five listed cases and specification-based inheritance overrides.