tasktree 0.0.20__tar.gz → 0.0.22__tar.gz

{tasktree-0.0.20 → tasktree-0.0.22}/.claude/settings.local.json

@@ -15,7 +15,9 @@
       "Bash(cat:*)",
       "Bash(tt --help:*)",
       "Bash(head:*)",
-      "Bash(wc:*)"
+      "Bash(wc:*)",
+      "Bash(athena status:*)",
+      "Bash(athena sync:*)"
     ]
   }
 }

{tasktree-0.0.20 → tasktree-0.0.22}/.github/workflows/test.yml

@@ -27,31 +27,26 @@ jobs:
       uses: astral-sh/setup-uv@v4
 
     - name: Install dependencies
-      run: |
-        uv pip install --system -e ".[dev]"
+      run: uv sync --extra dev
 
     - name: Pre-pull Docker images for E2E tests
       if: runner.os == 'Linux'
-      run: |
-        docker pull alpine:latest
+      run: docker pull alpine:latest
 
     - name: Run unit tests
-      run: |
-        python -m pytest tests/unit/ -v --tb=short
+      run: uv run pytest tests/unit/ --tb=short
 
     - name: Run integration tests
-      run: |
-        python -m pytest tests/integration/ -v --tb=short
+      run: uv run pytest tests/integration/ --tb=short
 
     - name: Run E2E Docker tests
       if: runner.os == 'Linux'
-      run: |
-        python -m pytest tests/e2e/ -v --tb=short
+      run: uv run pytest tests/e2e/ --tb=short
 
     - name: Test CLI commands
       run: |
-        python -m tasktree.cli --help
-        python -m tasktree.cli --list || true
+        uv run tt --help
+        uv run tt --list || true
 
   lint:
     runs-on: ubuntu-latest
@@ -67,9 +62,7 @@ jobs:
       uses: astral-sh/setup-uv@v4
 
     - name: Install dependencies
-      run: |
-        uv pip install --system -e ".[dev]"
+      run: uv sync --extra dev
 
     - name: Check code can be imported
-      run: |
-        python -c "from tasktree import Executor, Recipe, Task; print('Import successful')"
+      run: uv run python -c "from tasktree import Executor, Recipe, Task; print('Import successful')"

{tasktree-0.0.20 → tasktree-0.0.22}/.gitignore

@@ -157,6 +157,5 @@ example/.tasktree-state
 # Requirements files copied from GitHub issues (for driving Claude Code)
 requirements/*
 
-# UV lock file (optional - some prefer to commit this)
-# uv.lock
+.athena-cache
 

{tasktree-0.0.20 → tasktree-0.0.22}/CLAUDE.md

@@ -74,15 +74,30 @@ Your sponsor is not made of money! Try to minimise token useage, so that we can
 
 ## Development Commands
 
+## IMPORTANT! Tool use
+### Athena Code Knowledge
+This repo uses Athena to store and retrieve knowledge about the codebase. YOU SHOULD USE THE TOOL TO MAKE INQUIRIES ABOUT THE CODE.
+
+1. Find a function/class: `athena locate <function/class name>`
+2. Find information about what a function/class does:
+   - `athena info path/to/module.py:ClassName`
+   - `athena info path/to/module.py:ClassName.method`
+   - `athena info path/to/module.py:some_function`
+3. Search for relevant code information:
+   - `athena serch "generate JWT authentication tokens`
+4. AFTER code changes, run `athena status` to check which docs should have been updated
+5. AFTER checking/updating docs, run `athena sync` to register the changes
+
+**prefer this workflow to using native `grep` and `find` tools** for understanding the code.
+
 ### Testing
 ```bash
 python3 -m pytest tests/
 ```
-
-The project has **656 tests** across three categories:
-- **Unit tests** (`tests/unit/`): 15 test files covering parser, executor, graph, hasher, types, substitution, state
-- **Integration tests** (`tests/integration/`): 21 test files for CLI options, parameterized tasks, Docker, variables, arg validation
-- **E2E tests** (`tests/e2e/`): 5 test files for Docker volumes, ownership, environment, and basic functionality
+The project has tests across three categories:
+- **Unit tests** (`tests/unit/`): Should always be updated for any change. Makes up the bulk of code coverage
+- **Integration tests** (`tests/integration/`): Test changes using the Typer CliRunner to cover end-to-end workflows across multiple modules
+- **E2E tests** (`tests/e2e/`): Heavyweight tests that cover running the tool in a subprocess and/or containerized environment 
 
 ### Running the Application
 ```bash
@@ -139,6 +154,8 @@ environments:
   env-name:
     default: true  # Make this the default environment
     shell: /bin/bash  # Shell environment
+    preamble: |  # Optional preamble prepended to all commands
+      set -euo pipefail
     # OR
     dockerfile: path/to/Dockerfile  # Docker environment
     context: build-context-dir

tasktree-0.0.20/README.md → tasktree-0.0.22/PKG-INFO

@@ -1,3 +1,20 @@
+Metadata-Version: 2.4
+Name: tasktree
+Version: 0.0.22
+Summary: A task automation tool with incremental execution
+Requires-Python: >=3.11
+Requires-Dist: click>=8.1.0
+Requires-Dist: colorama>=0.4.6
+Requires-Dist: pathspec>=0.11.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: rich>=13.0.0
+Requires-Dist: typer>=0.9.0
+Provides-Extra: dev
+Requires-Dist: black>=26.1.0; extra == 'dev'
+Requires-Dist: pytest>=9.0.2; extra == 'dev'
+Requires-Dist: ruff>=0.14.14; extra == 'dev'
+Description-Content-Type: text/markdown
+
 # Task Tree (tt)
 
 [![Tests](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml/badge.svg)](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml)
@@ -240,20 +257,19 @@ tasks:
     cmd: go build -o dist/binary           # Command to execute
 ```
 
+**Task name constraints:**
+- Task names cannot contain dots (`.`) - they are reserved for namespacing imported tasks
+- Example: `build.release` is invalid as a task name, but valid as a reference to task `release` in namespace `build`
+
 ### Commands
 
-**Single-line commands** are executed directly via the configured shell:
+All commands are executed by writing them to temporary script files. This provides consistent behavior and better shell syntax support:
 
 ```yaml
 tasks:
   build:
     cmd: cargo build --release
-```
 
-**Multi-line commands** are written to temporary script files for proper execution:
-
-```yaml
-tasks:
   deploy:
     cmd: |
       mkdir -p dist
@@ -261,7 +277,7 @@ tasks:
       rsync -av dist/ server:/opt/app/
 ```
 
-Multi-line commands preserve shell syntax (line continuations, heredocs, etc.) and support shebangs on Unix/macOS.
+Commands preserve shell syntax (line continuations, heredocs, etc.) and support shebangs on Unix/macOS.
 
 Or use folded blocks for long single-line commands:
 
@@ -277,7 +293,7 @@ tasks:
 
 ### Execution Environments
 
-Configure custom shell environments for task execution:
+Configure custom shell environments for task execution. Use the `preamble` field to add initialization code to all commands:
 
 ```yaml
 environments:
@@ -285,17 +301,14 @@ environments:
 
   bash-strict:
     shell: bash
-    args: ['-c']              # For single-line: bash -c "command"
-    preamble: |               # For multi-line: prepended to script
+    preamble: |               # Prepended to all commands
       set -euo pipefail
 
   python:
     shell: python
-    args: ['-c']
 
   powershell:
     shell: powershell
-    args: ['-ExecutionPolicy', 'Bypass', '-Command']
     preamble: |
       $ErrorActionPreference = 'Stop'
 
@@ -324,8 +337,8 @@ tasks:
 4. Platform default (bash on Unix, cmd on Windows)
 
 **Platform defaults** when no environments are configured:
-- **Unix/macOS**: bash with `-c` args
-- **Windows**: cmd with `/c` args
+- **Unix/macOS**: bash
+- **Windows**: cmd
 
 ### Docker Environments
 
@@ -820,7 +833,7 @@ Hint: Define named outputs like: outputs: [{ missing: 'path/to/file' }]
 
 ### Self-References
 
-Tasks can reference their own named inputs and outputs using `{{ self.inputs.name }}` and `{{ self.outputs.name }}` templates. This eliminates repetition when paths contain variables or when tasks have multiple inputs/outputs.
+Tasks can reference their own inputs and outputs using `{{ self.inputs.name }}` (named access) or `{{ self.inputs.0 }}` (positional access) templates. This eliminates repetition when paths contain variables or when tasks have multiple inputs/outputs.
 
 **Named Inputs and Outputs:**
 
@@ -847,8 +860,10 @@ tasks:
 
 - **Defining named inputs**: `inputs: [{ name: "path/to/file" }]`
 - **Defining named outputs**: `outputs: [{ name: "path/to/file" }]`
-- **Referencing inputs**: `{{ self.inputs.input_name }}`
-- **Referencing outputs**: `{{ self.outputs.output_name }}`
+- **Defining anonymous inputs**: `inputs: ["path/to/file"]`
+- **Defining anonymous outputs**: `outputs: ["path/to/file"]`
+- **Referencing by name**: `{{ self.inputs.input_name }}` or `{{ self.outputs.output_name }}`
+- **Referencing by index**: `{{ self.inputs.0 }}` or `{{ self.outputs.1 }}` (0-based)
 - **Mixed format**: Can combine named and anonymous inputs/outputs in the same task
 
 **Why Use Self-References?**
@@ -957,6 +972,129 @@ tasks:
     cmd: build-tool --config {{ self.inputs.config }} --output {{ self.outputs.binary }}
 ```
 
+**Positional Index References:**
+
+In addition to named references, you can access inputs and outputs by their positional index using `{{ self.inputs.0 }}`, `{{ self.inputs.1 }}`, etc. This provides an alternative way to reference items, especially useful for:
+
+- **Anonymous inputs/outputs**: Reference items that don't have names
+- **Simple sequential access**: When order is more important than naming
+- **Mixed with named access**: Use both styles in the same task
+
+**Syntax:**
+
+```yaml
+tasks:
+  process:
+    inputs: ["file1.txt", "file2.txt", "file3.txt"]
+    outputs: ["output1.txt", "output2.txt"]
+    cmd: |
+      cat {{ self.inputs.0 }} {{ self.inputs.1 }} > {{ self.outputs.0 }}
+      cat {{ self.inputs.2 }} > {{ self.outputs.1 }}
+```
+
+Indices follow YAML declaration order, starting from 0 (zero-based indexing):
+- First input/output = index 0
+- Second input/output = index 1
+- Third input/output = index 2, etc.
+
+**Works with Both Named and Anonymous:**
+
+```yaml
+tasks:
+  build:
+    inputs:
+      - config: "build.yaml"  # Index 0, also accessible as {{ self.inputs.config }}
+      - "src/**/*.c"          # Index 1, ONLY accessible as {{ self.inputs.1 }}
+      - headers: "include/*.h" # Index 2, also accessible as {{ self.inputs.headers }}
+    outputs:
+      - "dist/app.js"         # Index 0
+      - bundle: "dist/bundle.js" # Index 1, also accessible as {{ self.outputs.bundle }}
+    cmd: |
+      # Mix positional and named references
+      build-tool \
+        --config {{ self.inputs.0 }} \
+        --sources {{ self.inputs.1 }} \
+        --headers {{ self.inputs.headers }} \
+        --output {{ self.outputs.bundle }}
+```
+
+**Same Item, Multiple Ways:**
+
+Named items can be accessed by both name and index:
+
+```yaml
+tasks:
+  copy:
+    inputs:
+      - source: data.txt
+    cmd: |
+      # These are equivalent:
+      cat {{ self.inputs.source }} > copy1.txt
+      cat {{ self.inputs.0 }} > copy2.txt
+```
+
+**With Variables and Arguments:**
+
+Positional references work with variable-expanded paths:
+
+```yaml
+variables:
+  version: "1.0"
+
+tasks:
+  package:
+    args: [platform]
+    inputs:
+      - "dist/app-{{ var.version }}.js"
+      - "dist/lib-{{ arg.platform }}.so"
+    outputs: ["release-{{ var.version }}-{{ arg.platform }}.tar.gz"]
+    cmd: tar czf {{ self.outputs.0 }} {{ self.inputs.0 }} {{ self.inputs.1 }}
+```
+
+**Index Boundaries:**
+
+Indices are validated before execution:
+
+```yaml
+tasks:
+  build:
+    inputs: ["file1.txt", "file2.txt"]
+    cmd: cat {{ self.inputs.5 }}  # Error: index 5 out of bounds!
+```
+
+Error message:
+```
+Task 'build' references input index '5' but only has 2 inputs (indices 0-1)
+```
+
+**Empty Lists:**
+
+Referencing an index when no inputs/outputs exist:
+
+```yaml
+tasks:
+  generate:
+    cmd: echo "test" > {{ self.outputs.0 }}  # Error: no outputs defined!
+```
+
+Error message:
+```
+Task 'generate' references output index '0' but has no outputs defined
+```
+
+**When to Use Index References:**
+
+- **Anonymous items**: Only way to reference inputs/outputs without names
+- **Order-based processing**: When the sequence matters more than naming
+- **Simple tasks**: Quick access without defining names
+- **Compatibility**: Accessing items in legacy YAML that uses anonymous format
+
+**When to Use Named References:**
+
+- **Clarity**: Names make commands more readable (`{{ self.inputs.config }}` vs `{{ self.inputs.2 }}`)
+- **Maintainability**: Adding/removing items doesn't break indices
+- **Complex tasks**: Many inputs/outputs are easier to manage with names
+
 **Error Messages:**
 
 If you reference a non-existent input or output:
@@ -996,18 +1134,21 @@ Hint: Define named inputs like: inputs: [{ src: 'file.txt' }]
 
 **Key Behaviors:**
 
+- **Two access methods**: Reference by name (`{{ self.inputs.name }}`) or by index (`{{ self.inputs.0 }}`)
 - **Template resolution**: Self-references are resolved during dependency graph planning
 - **Substitution order**: Variables → Dependency outputs → Self-references → Arguments/Environment
-- **Fail-fast validation**: Errors are caught before execution begins
-- **Clear error messages**: Lists available names if reference doesn't exist
+- **Fail-fast validation**: Errors are caught before execution begins (missing names, out-of-bounds indices)
+- **Clear error messages**: Lists available names/indices if reference doesn't exist
 - **Backward compatible**: Existing anonymous inputs/outputs work unchanged
 - **State tracking**: Works correctly with incremental execution and freshness checks
+- **Index order**: Positional indices follow YAML declaration order (0-based)
 
 **Limitations:**
 
-- **Anonymous not referenceable**: Only named inputs/outputs can be referenced
+- **Anonymous not referenceable by name**: Anonymous inputs/outputs cannot be referenced by name (use positional index instead: `{{ self.inputs.0 }}`)
 - **Case sensitive**: `{{ self.inputs.Src }}` and `{{ self.inputs.src }}` are different
 - **Argument defaults**: Self-references in argument defaults are not supported (arguments are evaluated before self-references)
+- **No negative indices**: Python-style negative indexing (`{{ self.inputs.-1 }}`) is not supported
 
 **Use Cases:**
 

tasktree-0.0.20/PKG-INFO → tasktree-0.0.22/README.md

@@ -1,18 +1,3 @@
-Metadata-Version: 2.4
-Name: tasktree
-Version: 0.0.20
-Summary: A task automation tool with incremental execution
-Requires-Python: >=3.11
-Requires-Dist: click>=8.1.0
-Requires-Dist: colorama>=0.4.6
-Requires-Dist: pathspec>=0.11.0
-Requires-Dist: pyyaml>=6.0
-Requires-Dist: rich>=13.0.0
-Requires-Dist: typer>=0.9.0
-Provides-Extra: dev
-Requires-Dist: pytest>=9.0.2; extra == 'dev'
-Description-Content-Type: text/markdown
-
 # Task Tree (tt)
 
 [![Tests](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml/badge.svg)](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml)
@@ -255,20 +240,19 @@ tasks:
     cmd: go build -o dist/binary           # Command to execute
 ```
 
+**Task name constraints:**
+- Task names cannot contain dots (`.`) - they are reserved for namespacing imported tasks
+- Example: `build.release` is invalid as a task name, but valid as a reference to task `release` in namespace `build`
+
 ### Commands
 
-**Single-line commands** are executed directly via the configured shell:
+All commands are executed by writing them to temporary script files. This provides consistent behavior and better shell syntax support:
 
 ```yaml
 tasks:
   build:
     cmd: cargo build --release
-```
 
-**Multi-line commands** are written to temporary script files for proper execution:
-
-```yaml
-tasks:
   deploy:
     cmd: |
       mkdir -p dist
@@ -276,7 +260,7 @@ tasks:
       rsync -av dist/ server:/opt/app/
 ```
 
-Multi-line commands preserve shell syntax (line continuations, heredocs, etc.) and support shebangs on Unix/macOS.
+Commands preserve shell syntax (line continuations, heredocs, etc.) and support shebangs on Unix/macOS.
 
 Or use folded blocks for long single-line commands:
 
@@ -292,7 +276,7 @@ tasks:
 
 ### Execution Environments
 
-Configure custom shell environments for task execution:
+Configure custom shell environments for task execution. Use the `preamble` field to add initialization code to all commands:
 
 ```yaml
 environments:
@@ -300,17 +284,14 @@ environments:
 
   bash-strict:
     shell: bash
-    args: ['-c']              # For single-line: bash -c "command"
-    preamble: |               # For multi-line: prepended to script
+    preamble: |               # Prepended to all commands
       set -euo pipefail
 
   python:
     shell: python
-    args: ['-c']
 
   powershell:
     shell: powershell
-    args: ['-ExecutionPolicy', 'Bypass', '-Command']
     preamble: |
       $ErrorActionPreference = 'Stop'
 
@@ -339,8 +320,8 @@ tasks:
 4. Platform default (bash on Unix, cmd on Windows)
 
 **Platform defaults** when no environments are configured:
-- **Unix/macOS**: bash with `-c` args
-- **Windows**: cmd with `/c` args
+- **Unix/macOS**: bash
+- **Windows**: cmd
 
 ### Docker Environments
 
@@ -835,7 +816,7 @@ Hint: Define named outputs like: outputs: [{ missing: 'path/to/file' }]
 
 ### Self-References
 
-Tasks can reference their own named inputs and outputs using `{{ self.inputs.name }}` and `{{ self.outputs.name }}` templates. This eliminates repetition when paths contain variables or when tasks have multiple inputs/outputs.
+Tasks can reference their own inputs and outputs using `{{ self.inputs.name }}` (named access) or `{{ self.inputs.0 }}` (positional access) templates. This eliminates repetition when paths contain variables or when tasks have multiple inputs/outputs.
 
 **Named Inputs and Outputs:**
 
@@ -862,8 +843,10 @@ tasks:
 
 - **Defining named inputs**: `inputs: [{ name: "path/to/file" }]`
 - **Defining named outputs**: `outputs: [{ name: "path/to/file" }]`
-- **Referencing inputs**: `{{ self.inputs.input_name }}`
-- **Referencing outputs**: `{{ self.outputs.output_name }}`
+- **Defining anonymous inputs**: `inputs: ["path/to/file"]`
+- **Defining anonymous outputs**: `outputs: ["path/to/file"]`
+- **Referencing by name**: `{{ self.inputs.input_name }}` or `{{ self.outputs.output_name }}`
+- **Referencing by index**: `{{ self.inputs.0 }}` or `{{ self.outputs.1 }}` (0-based)
 - **Mixed format**: Can combine named and anonymous inputs/outputs in the same task
 
 **Why Use Self-References?**
@@ -972,6 +955,129 @@ tasks:
     cmd: build-tool --config {{ self.inputs.config }} --output {{ self.outputs.binary }}
 ```
 
+**Positional Index References:**
+
+In addition to named references, you can access inputs and outputs by their positional index using `{{ self.inputs.0 }}`, `{{ self.inputs.1 }}`, etc. This provides an alternative way to reference items, especially useful for:
+
+- **Anonymous inputs/outputs**: Reference items that don't have names
+- **Simple sequential access**: When order is more important than naming
+- **Mixed with named access**: Use both styles in the same task
+
+**Syntax:**
+
+```yaml
+tasks:
+  process:
+    inputs: ["file1.txt", "file2.txt", "file3.txt"]
+    outputs: ["output1.txt", "output2.txt"]
+    cmd: |
+      cat {{ self.inputs.0 }} {{ self.inputs.1 }} > {{ self.outputs.0 }}
+      cat {{ self.inputs.2 }} > {{ self.outputs.1 }}
+```
+
+Indices follow YAML declaration order, starting from 0 (zero-based indexing):
+- First input/output = index 0
+- Second input/output = index 1
+- Third input/output = index 2, etc.
+
+**Works with Both Named and Anonymous:**
+
+```yaml
+tasks:
+  build:
+    inputs:
+      - config: "build.yaml"  # Index 0, also accessible as {{ self.inputs.config }}
+      - "src/**/*.c"          # Index 1, ONLY accessible as {{ self.inputs.1 }}
+      - headers: "include/*.h" # Index 2, also accessible as {{ self.inputs.headers }}
+    outputs:
+      - "dist/app.js"         # Index 0
+      - bundle: "dist/bundle.js" # Index 1, also accessible as {{ self.outputs.bundle }}
+    cmd: |
+      # Mix positional and named references
+      build-tool \
+        --config {{ self.inputs.0 }} \
+        --sources {{ self.inputs.1 }} \
+        --headers {{ self.inputs.headers }} \
+        --output {{ self.outputs.bundle }}
+```
+
+**Same Item, Multiple Ways:**
+
+Named items can be accessed by both name and index:
+
+```yaml
+tasks:
+  copy:
+    inputs:
+      - source: data.txt
+    cmd: |
+      # These are equivalent:
+      cat {{ self.inputs.source }} > copy1.txt
+      cat {{ self.inputs.0 }} > copy2.txt
+```
+
+**With Variables and Arguments:**
+
+Positional references work with variable-expanded paths:
+
+```yaml
+variables:
+  version: "1.0"
+
+tasks:
+  package:
+    args: [platform]
+    inputs:
+      - "dist/app-{{ var.version }}.js"
+      - "dist/lib-{{ arg.platform }}.so"
+    outputs: ["release-{{ var.version }}-{{ arg.platform }}.tar.gz"]
+    cmd: tar czf {{ self.outputs.0 }} {{ self.inputs.0 }} {{ self.inputs.1 }}
+```
+
+**Index Boundaries:**
+
+Indices are validated before execution:
+
+```yaml
+tasks:
+  build:
+    inputs: ["file1.txt", "file2.txt"]
+    cmd: cat {{ self.inputs.5 }}  # Error: index 5 out of bounds!
+```
+
+Error message:
+```
+Task 'build' references input index '5' but only has 2 inputs (indices 0-1)
+```
+
+**Empty Lists:**
+
+Referencing an index when no inputs/outputs exist:
+
+```yaml
+tasks:
+  generate:
+    cmd: echo "test" > {{ self.outputs.0 }}  # Error: no outputs defined!
+```
+
+Error message:
+```
+Task 'generate' references output index '0' but has no outputs defined
+```
+
+**When to Use Index References:**
+
+- **Anonymous items**: Only way to reference inputs/outputs without names
+- **Order-based processing**: When the sequence matters more than naming
+- **Simple tasks**: Quick access without defining names
+- **Compatibility**: Accessing items in legacy YAML that uses anonymous format
+
+**When to Use Named References:**
+
+- **Clarity**: Names make commands more readable (`{{ self.inputs.config }}` vs `{{ self.inputs.2 }}`)
+- **Maintainability**: Adding/removing items doesn't break indices
+- **Complex tasks**: Many inputs/outputs are easier to manage with names
+
 **Error Messages:**
 
 If you reference a non-existent input or output:
@@ -1011,18 +1117,21 @@ Hint: Define named inputs like: inputs: [{ src: 'file.txt' }]
 
 **Key Behaviors:**
 
+- **Two access methods**: Reference by name (`{{ self.inputs.name }}`) or by index (`{{ self.inputs.0 }}`)
 - **Template resolution**: Self-references are resolved during dependency graph planning
 - **Substitution order**: Variables → Dependency outputs → Self-references → Arguments/Environment
-- **Fail-fast validation**: Errors are caught before execution begins
-- **Clear error messages**: Lists available names if reference doesn't exist
+- **Fail-fast validation**: Errors are caught before execution begins (missing names, out-of-bounds indices)
+- **Clear error messages**: Lists available names/indices if reference doesn't exist
 - **Backward compatible**: Existing anonymous inputs/outputs work unchanged
 - **State tracking**: Works correctly with incremental execution and freshness checks
+- **Index order**: Positional indices follow YAML declaration order (0-based)
 
 **Limitations:**
 
-- **Anonymous not referenceable**: Only named inputs/outputs can be referenced
+- **Anonymous not referenceable by name**: Anonymous inputs/outputs cannot be referenced by name (use positional index instead: `{{ self.inputs.0 }}`)
 - **Case sensitive**: `{{ self.inputs.Src }}` and `{{ self.inputs.src }}` are different
 - **Argument defaults**: Self-references in argument defaults are not supported (arguments are evaluated before self-references)
+- **No negative indices**: Python-style negative indexing (`{{ self.inputs.-1 }}`) is not supported
 
 **Use Cases:**
 

tasktree-0.0.22/__init__.py

@@ -0,0 +1,3 @@
+"""
+@athena: a46f4c60df41
+"""