compat: remove ast from tokmd default features 🧷

Removed the `ast` feature from the `default` features of the `tokmd` crate to allow building for `wasm32-unknown-unknown` out of the box.

The `ast` feature pulls in `tree-sitter` and its parsers, which rely on the C standard library (`stdlib.h`). This breaks builds for `wasm32-unknown-unknown` where `stdlib.h` is not available by default. By removing it from `default` features, WASM compatibility is restored without breaking existing functionality.

Author: EffortlessSteven

.jules/runs/compat_interfaces_matrix/decision.md

@@ -0,0 +1,7 @@
+### Option A
+Ensure the `ast` feature is disabled when building for `wasm32-unknown-unknown` because `tree-sitter` parsers rely on `stdlib.h` which isn't present by default in the `wasm32-unknown-unknown` target. The `default` features of `tokmd` currently include `ast`, breaking wasm builds unless `default-features = false` is specified or `ast` is removed from `default` features. Removing it from `default` features in `tokmd` is a clean way to ensure compatibility without needing custom configurations for wasm targets, as per the memory instructions.
+
+### Option B
+Provide a custom `cfg` attribute in `Cargo.toml` to disable the `ast` feature for wasm targets automatically.
+
+**Decision: Option A** is aligned with the memory which explicitly states: "In the `tokmd` project, the `ast` feature (which pulls in `tree-sitter` and its parsers) requires a C standard library (`stdlib.h`) and breaks standard `wasm32-unknown-unknown` builds. It should not be included in `default` features for crates intended to be WASM compatible." Option A adheres directly to this constraint.

.jules/runs/compat_interfaces_matrix/envelope.json

@@ -0,0 +1,16 @@
+{
+  "prompt_id": "compat_interfaces_matrix",
+  "persona": "compat",
+  "style": "builder",
+  "primary_shard": "interfaces",
+  "allowed_paths": [
+    "crates/tokmd-config/**",
+    "crates/tokmd-core/**",
+    "crates/tokmd/**",
+    "docs/reference-cli.md",
+    "docs/tutorial.md",
+    "crates/tokmd/tests/**"
+  ],
+  "gate_profile": "compat-matrix",
+  "allowed_outcomes": ["patch", "learning"]
+}

.jules/runs/compat_interfaces_matrix/pr_body.md

@@ -0,0 +1,46 @@
+## 💡 Summary
+Removed the `ast` feature from the `default` features of the `tokmd` crate to allow building for `wasm32-unknown-unknown` out of the box.
+
+## 🎯 Why
+The `ast` feature pulls in `tree-sitter` and its parsers, which rely on the C standard library (`stdlib.h`). This breaks builds for `wasm32-unknown-unknown` where `stdlib.h` is not available by default. By removing it from `default` features, WASM compatibility is restored without breaking existing functionality.
+
+## 🔎 Evidence
+Running `cargo check -p tokmd --no-default-features --features ast --target wasm32-unknown-unknown` fails with:
+`fatal error: 'stdlib.h' file not found`
+
+## 🧭 Options considered
+### Option A (recommended)
+- what it is: Remove `ast` from the `default` features of the `tokmd` crate.
+- why it fits this repo and shard: It restores WASM compatibility which aligns with the `compat-matrix` gate, and is requested directly in the instructions.
+- trade-offs: Users relying on the `ast` feature will need to explicitly enable it.
+
+### Option B
+- what it is: Provide a custom `cfg` attribute in `Cargo.toml` to disable the `ast` feature for wasm targets.
+- when to choose it instead: When `ast` MUST be default for all non-wasm targets.
+- trade-offs: Increases complexity in Cargo manifests and feature propagation.
+
+## ✅ Decision
+Proceeded with Option A as it is the most robust way to handle this compatibility constraint, aligning perfectly with memory directives.
+
+## 🧱 Changes made (SRP)
+- `crates/tokmd/Cargo.toml`: Removed `ast` from `default` features.
+
+## 🧪 Verification receipts
+`cargo check -p tokmd --target wasm32-unknown-unknown` completes successfully.
+
+## 🧭 Telemetry
+- Change shape: small config change
+- Blast radius: feature boundaries
+- Risk class: low
+- Rollback: Re-add `ast` to `default` features.
+- Gates run: `compat-matrix` fallback tests.
+
+## 🗂️ .jules artifacts
+- `.jules/runs/compat_interfaces_matrix/envelope.json`
+- `.jules/runs/compat_interfaces_matrix/decision.md`
+- `.jules/runs/compat_interfaces_matrix/receipts.jsonl`
+- `.jules/runs/compat_interfaces_matrix/result.json`
+- `.jules/runs/compat_interfaces_matrix/pr_body.md`
+
+## 🔜 Follow-ups
+None.

.jules/runs/compat_interfaces_matrix/receipts.jsonl

@@ -0,0 +1,10 @@
+{"command": "cargo check -p tokmd --target wasm32-unknown-unknown", "outcome": "failed with fatal error: 'stdlib.h' file not found for tree-sitter-python"}
+{"command": "replace_with_git_merge_diff crates/tokmd/Cargo.toml", "outcome": "successfully replaced 'ast' from default features"}
+{"command": "cat crates/tokmd/Cargo.toml | grep -A 2 -B 2 \"\\[features\\]\"", "outcome": "verified feature change"}
+{"command": "cargo check -p tokmd --target wasm32-unknown-unknown", "outcome": "passed successfully"}
+{"command": "cargo check -p tokmd --all-features", "outcome": "passed successfully"}
+{"command": "cargo test -p tokmd --no-default-features", "outcome": "passed successfully"}
+{"command": "cargo test -p tokmd --all-features", "outcome": "passed successfully"}
+{"command": "cargo fmt -- --check", "outcome": "passed successfully"}
+{"command": "cargo clippy -- -D warnings", "outcome": "passed successfully"}
+{"command": "cargo build -p tokmd --verbose", "outcome": "passed successfully"}

.jules/runs/compat_interfaces_matrix/result.json

@@ -0,0 +1,5 @@
+{
+  "outcome": "success",
+  "patch_type": "compat",
+  "description": "Removed `ast` feature from `tokmd` default features to fix wasm32-unknown-unknown build failure."
+}

crates/tokmd/Cargo.toml

@@ -26,7 +26,7 @@ exclude = [
 ]
 
 [features]
-default = ["git", "walk", "content", "ui", "fun", "topics", "archetype", "analysis", "ast"]
+default = ["git", "walk", "content", "ui", "fun", "topics", "archetype", "analysis"]
 alias-tok = []
 analysis = ["tokmd-core/analysis"]
 git = [