Add lexical scope support to AST nodes

.claude/skills/review-code/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: review-code
+description: Reviews code changes for bugs, style issues, and correctness. Use when reviewing code, PRs, or asking for a code review.
+allowed-tools: Read, Grep, Glob, Bash
+---
+
+Review the code changes specified by `$ARGUMENTS` (a file path, directory, or git ref range). If no arguments are provided, review all uncommitted changes using `git diff` and `git diff --cached`.
+
+## Review Checklist
+
+### Correctness
+- Logic errors, off-by-one mistakes, missing edge cases
+- Proper handling of `None`/`undef` values throughout the AST pipeline
+- Parse tree visitor methods in `builder.py` must match grammar rule names in `grammar.py`
+- AST node dataclass fields must match what the builder produces
+
+### Parser & Grammar
+- New grammar rules must be reachable from `openscad_language` or `openscad_language_with_comments`
+- Arpeggio ordering matters: alternatives are tried in order, put more specific rules first
+- Ensure `comment` and `whitespace_only` skip rules aren't accidentally changed
+- Token rules using `Not()` must not create ambiguity with other tokens
+
+### AST Layer
+- New node types must inherit from `ASTNode` and use `@dataclass`
+- Nodes must be serializable (check `serialization.py` compatibility)
+- Source position tracking via `SourceMap` must be preserved through transformations
+- Scope handling: verify parent/child scope relationships are set correctly
+
+### Python Style
+- Type annotations on public API functions
+- Dataclass fields should have sensible defaults where appropriate
+- Avoid mutable default arguments (use `field(default_factory=...)`)
+- Follow existing patterns in the codebase rather than introducing new conventions
+
+### Testing
+- New grammar rules need corresponding test cases in `tests/`
+- Test both valid parses and expected parse failures
+- AST builder changes need tests verifying node structure
+- Use the existing `parser` and `parser_reduced` fixtures from `conftest.py`
+
+## Output Format
+
+Organize findings by severity:
+
+1. **Bugs** - Will cause incorrect behavior or crashes
+2. **Issues** - Could cause problems in some cases
+3. **Suggestions** - Improvements to readability, style, or maintainability
+
+For each finding, include the file path, line number, and a specific fix.

.github/workflows/publish.yml

@@ -0,0 +1,45 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install uv
+        run: pip install uv
+
+      - name: Build package
+        run: uv build
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Download build artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1