Document modulations as ShapeKernel abstraction over PicoGK voxel operations

[Copilot]

The modulations section lacked context about how modulations relate to PicoGK's underlying geometry engine.

Changes

Added introductory paragraphs to the "Line and Surface Modulations" section explaining:

• Architectural relationship: Modulations provide parametric control at the ShapeKernel layer before shapes are rendered into PicoGK's voxel representation
• Abstraction level: While PicoGK handles low-level voxel operations (Boolean, offsets, rendering), modulations define how shape dimensions (radius, width, height) vary smoothly across surfaces
• Practical approach: Mathematical functions and point lists describe geometric variations (tapered cylinders, variable-thickness pipes, periodic features) that translate to voxel fields

The existing technical documentation is unchanged; this addition contextualizes modulations within the PicoGK architecture.

Original prompt

can you describe modulations in picogk. @leap71/LEAP71_ShapeKernel/files/Documentation/README-ReadingDetails.md

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.