Bump braces and gulp in /inst/htmlwidgets/neurosurface

.Rbuildignore

@@ -6,3 +6,11 @@
 ^codecov.yml
 ^README.Rmd
 ^.travis.yml
+inst/htmlwidgets/neurosurface/node_modules
+testshiny
+testshiny/test_shiny.R
+.cursor$
+^CLAUDE\.md$
+^CRAN_prompt\.md$
+^cran_check\.log$
+^cran_check_final\.log$

.cursor/rules/roxygendocs.mdc

@@ -0,0 +1,25 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+Rules for Documenting S4 Generics and Methods in R using roxygen2:
+
+Centralize Documentation in Generic: The primary documentation (@description, @details, @param for generic parameters, @return, @examples, etc.) MUST reside in the roxygen block of the S4 generic function.
+
+Use Consistent @rdname: The generic function and ALL its associated S4 methods MUST use the exact same @rdname tag value. This ensures they all contribute to a single help file.
+
+Minimize Method Documentation: Roxygen blocks for S4 methods should be minimal. Typically, they only require:
+
+@rdname [value] (Matching the generic's @rdname).
+
+@export (Only if the method itself needs exporting, which is less common than exporting the generic).
+
+Document ONLY New Method Parameters: If an S4 method signature includes additional parameters not present in the generic, document only these new parameters using @param tags within that method's roxygen block. Do not re-document parameters inherited from the generic.
+
+Avoid Redundant Core Tags in Methods: Do NOT add tags like @description, @return, or @param (for generic parameters) to method documentation, as the shared @rdname links to the generic's definition. This prevents conflicting or duplicate information in the final help file.
+
+Use @details or @note for Method Specifics: If a particular method has unique behavior or implementation details critical for the user to know, add this information to the method's roxygen block using tags like @details or @note. This information should supplement, not replace or conflict with, the generic's 
+documentation.
+
+Never use "dontrun", use "donttest" instead if it's a long-running task. All examples should in theory be runnable.

.gitignore

@@ -0,0 +1,4 @@
+.Rproj.user
+.Rhistory
+.RData
+.Ruserdata

CLAUDE.md

@@ -0,0 +1,109 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+`neurosurf` is an R package for surface-based neuroimaging data analysis. It provides data structures and visualization tools for working with triangle mesh surfaces (e.g., cortical surfaces) with support for FreeSurfer and GIFTI formats.
+
+## Key Commands
+
+### Package Development
+```bash
+# Install dependencies and build package
+R -e "devtools::install_deps()"
+R -e "devtools::build()"
+
+# Check package (runs R CMD check)
+R -e "devtools::check()"
+
+# Run tests
+R -e "devtools::test()"
+
+# Run a single test file
+R -e "testthat::test_file('tests/testthat/test_boundaries_methods.R')"
+
+# Document package (generate/update roxygen documentation)
+R -e "devtools::document()"
+
+# Build and reload package
+R -e "devtools::load_all()"
+```
+
+### JavaScript Development (for htmlwidgets)
+```bash
+# Navigate to JavaScript source
+cd inst/htmlwidgets/neurosurface
+
+# Install dependencies
+npm install
+
+# Build JavaScript bundle
+npm run build
+```
+
+## Architecture
+
+### R Package Structure
+- **S4 Classes**: The package uses S4 object-oriented programming extensively
+  - Core geometry classes: `SurfaceGeometry`, `NeuroSurface`, `ColorMappedNeuroSurface`
+  - Vector classes: `NeuroSurfaceVector`, `BilatNeuroSurfaceVector`
+  - ROI classes: `ROISurface`, `ROISurfaceVector`
+  - File format classes for FreeSurfer, GIFTI, AFNI, and NIML formats
+
+- **Key Components**:
+  - `geometry.R`: Core surface geometry operations and data structures
+  - `neuro_surface.R`: Surface data mapping and visualization structures
+  - `surfwidget.R`: Interactive 3D visualization using htmlwidgets
+  - `Searchlight.R`: Surface-based searchlight analysis for machine learning
+  - `neighborhood.R`: Graph-based neighborhood computations on surfaces
+  - `IO.R`: File I/O for various surface formats
+
+### JavaScript/HTMLWidget Architecture
+- Uses Three.js for 3D rendering
+- Tweakpane for UI controls
+- Built with Rollup bundler
+- Main viewer: `inst/htmlwidgets/neurosurface/src/NeuroSurfaceViewer.js`
+
+## Documentation Guidelines
+
+When documenting S4 methods (per `.cursor/rules/roxygendocs.mdc`):
+- Document parameters, description, and examples ONLY in the generic function
+- Methods should only have `@rdname` matching the generic and `@export` if needed
+- Use `@details` or `@note` in methods only for method-specific behavior
+- Never use `@dontrun`, use `@donttest` for long-running examples
+
+## Testing
+
+Tests use `testthat` framework and are located in `tests/testthat/`. Key test areas:
+- Boundary detection algorithms
+- File I/O for different formats
+- Neighborhood graph computations
+- Searchlight analysis
+- Surface smoothing operations
+
+## Dependencies
+
+Key R dependencies:
+- `igraph`: Graph operations on surface meshes
+- `rgl`: 3D rendering (backend)
+- `Rvcg`: Mesh operations (smoothing, remeshing)
+- `Matrix`: Sparse matrix operations
+- `htmlwidgets`: Interactive visualizations
+- `neuroim2`: Neuroimaging data structures (custom package)
+
+## File Formats
+
+The package supports:
+- FreeSurfer surface formats (ASCII and binary)
+- GIFTI surface format
+- AFNI/SUMA surface formats
+- NIML format
+
+## HTMLWidget Integration
+
+The `surfwidget()` function creates interactive 3D visualizations. Key features:
+- Curvature-based shading (computed automatically for `SurfaceGeometry` objects)
+- Multiple color mapping options
+- Interactive controls via Tweakpane
+- Support for bilateral surface display