Add comprehensive tokenizer unit tests

Added 27 new tests (86 -> 113 total) covering:
- Template strings (t-strings) for Python 3.14+
- Raw template strings (rt/tr prefixes)
- Multiline template strings
- Matrix multiply operator (@)
- Matrix multiply assignment operator (@=)
- All 39 Python keywords
- Soft keywords as identifiers
- Unicode identifiers (Greek, Japanese, Chinese)
- Complex number literals
- Numbers with leading zeros
- All escape sequences in strings
- Line continuation in expressions
- Mixed tabs/spaces indentation
- Empty f-strings and template strings
- Deeply nested f-strings
- F-strings with colons in expressions
- Very long identifiers, strings, and numbers
- Named Unicode escapes
- Multiple operators without spaces
- Chained comparison operators
- All bitwise operators
- All assignment operators

Part of: pyright-rzw (Parser Component Test Coverage)

Author: Graham Wheeler

.beads/issues.jsonl

@@ -0,0 +1,40 @@
+# Agent Instructions
+
+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
+