windjammer 0.48.0

A simple language inspired by Go, Ruby, and Elixir that transpiles to Rust - 80% of Rust's power with 20% of the complexity
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65

# Agent Instructions

**Read the [windjammer-engineering skill](../.cursor/skills/windjammer-engineering/SKILL.md) before starting work.**

This project uses **bd** (beads) for issue tracking. Run `bd onboard` to get started.

## Quick Reference

```bash
bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --status in_progress  # Claim work
bd close <id>         # Complete work
bd sync               # Sync with git
```

## Landing the Plane (Session Completion)

**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.

**MANDATORY WORKFLOW:**

1. **File issues for remaining work** - Create issues for anything that needs follow-up
2. **Run quality gates** (if code changed) - Tests, linters, builds
3. **Update issue status** - Close finished work, update in-progress items
4. **PUSH TO REMOTE** - This is MANDATORY:
   ```bash
   git pull --rebase
   bd sync
   git push
   git status  # MUST show "up to date with origin"
   ```
5. **Clean up** - Clear stashes, prune remote branches
6. **Verify** - All changes committed AND pushed
7. **Hand off** - Provide context for next session

**CRITICAL RULES:**
- Work is NOT complete until `git push` succeeds
- NEVER stop before pushing - that leaves work stranded locally
- NEVER say "ready to push when you are" - YOU must push
- If push fails, resolve and retry until it succeeds

Use 'bd' for task tracking

## Compiler tests

Add `tests/your_feature_test.rs` — `build.rs` picks it up automatically. No edits to `all.rs` or `tests/lib.rs`.

**Canonical full suite:**

```bash
cargo test --release --test all
```

See `tests/README.md` for suite features and filtering.

Compiler-only changes: tests + `cargo test --release --test all` in `windjammer/` are sufficient.

When fixes enable or change player-visible behavior in **Breach Protocol** or the engine render path, agents must validate through the game — not only unit tests:

1. Build the game: `wj game build --release` in `../breach-protocol/`
2. Headless playthrough with screenshots (see `../breach-protocol/AGENTS.md`)
3. Dual-persona jury per `../.cursor/rules/dual-persona-jury-evaluation.mdc`

Do not claim rendering or gameplay fixes are done without screenshot evidence and three-tier verdict.