Merge branch dev into published

Author: PEZ

.github/instructions/workspace-e2e-testing-memory.instructions.md

@@ -0,0 +1,42 @@
+---
+description: 'E2E testing patterns and best practices for Calva extension development.'
+applyTo: '**/src/extension-test/e2e,package.json'
+---
+
+# E2E Testing Memory
+
+Patterns for reliable end-to-end testing and debugging workflows.
+
+## Use Containerized Test Runner
+Always use the containerized test runner to reproduce CI conditions exactly:
+
+```bash
+npm run e2e-test-containerized
+```
+
+**Why:** The containerized runner can use Insiders even if it is being used on the host machine.
+
+## Test Both Development and Production Scenarios
+E2E tests should cover both:
+- **Development mode**: `extensionDevelopmentPath` for source code testing
+- **Production mode**: VSIX package testing (what users actually install)
+
+## Use npm Scripts for Containerized Testing
+Always use npm scripts rather than running Docker commands directly:
+- `npm run e2e-test-containerized` - for containerized testing
+
+This ensures proper environment setup and dependency management.
+
+## Environment Variable Debugging
+When debugging CI failures related to environment variables:
+- Use exact CI argument reproduction: `npm run e2e-test-containerized -- --ci`
+- Check JavaScript variable access syntax: `process.env.VARIABLE_NAME` not `process.env[VARIABLE_NAME]`
+- Verify variable scoping in launch scripts
+
+## Data-Oriented E2E Debugging
+Follow the general debugging workflow for E2E issues:
+1. **Gather context** - understand CI vs local environment differences
+2. **Reproduce precisely** - use containerized runner with exact CI conditions
+3. **Analyze data flow** - trace through launch.js and test setup
+4. **Apply targeted fix** - address root cause in environment/configuration
+5. **Validate thoroughly** - test with both development and CI scenarios

.github/instructions/workspace-memory.instructions.md

@@ -0,0 +1,29 @@
+---
+description: 'A memory for the AI agent working in this project. See also the prompt `add-workspace-memory`.'
+applyTo: '**'
+---
+
+# Lessons learned and Best Practices for working with Calva
+
+
+## Problem-Solving Workflow
+
+### Data-Oriented Debugging Approach
+1. **Gather context first** - understand the difference between failing and working environments
+2. **Reproduce precisely** - use the exact same conditions as the failing environment
+3. **Analyze the data flow** - understand what's different about the failing path
+4. **Apply targeted fix** - address the root cause, not just symptoms
+5. **Validate thoroughly** - test the fix in the same conditions where it originally failed
+
+This follows Rich Hickey's thinking: understand the problem space before attempting solutions.
+
+## Development Environment
+
+### Interactive Programming Philosophy
+Remember that the human and the system (the Calva extension under development) are your sources of truth.
+
+### Joyride Integration
+Joyride gives you access to the extension host and VS Code APIs (sadly not the Development Extension host, though). You can create "tools" you need for your workflow, as Joyride is a bit of a DIY MCP server for VS Code itself.
+
+
+

CHANGELOG.md

@@ -4,6 +4,11 @@ Changes to Calva.
 
 ## [Unreleased]
 
+## [2.0.525] - 2025-08-30
+
+- Bump deps.clj.jar to v1.12.2.1565
+- Fix: [delete previous word incongruence between Calva and plain text in comments](https://github.com/BetterThanTomorrow/calva/issues/2912)
+
 ## [2.0.524] - 2025-08-16
 
 - Bump deps.clj.jar to v1.12.1.1561

deps-clj-version

@@ -1 +1 @@
-v1.12.1.1561
+v1.12.2.1565