Pass globals context to env block template rendering

[anticomputer]

Problem

Task env: blocks use swap_env() for template rendering, but swap_env only has access to the env() function -- not globals. This means {{ globals.X }} references in env blocks raise UndefinedError, even though they work fine in user_prompt blocks.

This matters for taskflows that need to pass global variables into container configuration (e.g. using a GHSA ID as a container persist key).

Fix

• swap_env() now accepts an optional context dict
• TmpEnv accepts and forwards context to swap_env()
• The runner passes {'globals': global_variables} when constructing TmpEnv

Backward compatible: context defaults to None, all existing env() calls work unchanged.

[Copilot]

Pull request overview

Enables task env: block template rendering to access globals (in addition to env()), aligning env rendering capabilities with user_prompt templating.

Changes:

• Extended swap_env() to accept an optional rendering context and pass it into Jinja rendering.
• Updated TmpEnv to accept/forward the optional context when rendering environment variable templates.
• Passed {"globals": global_variables} from the runner when constructing TmpEnv.

Show a summary per file

File	Description
src/seclab_taskflow_agent/runner.py	Passes globals into TmpEnv so task env: templates can reference globals.*.
src/seclab_taskflow_agent/env_utils.py	Adds optional template context support to swap_env()/TmpEnv and renders env values with that context.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 3

[Copilot]

Pull request overview

Enables Jinja template rendering inside task env: blocks to access globals (matching user_prompt behavior) by threading a caller-provided context through swap_env()/TmpEnv.

Changes:

• Add optional context parameter to swap_env() and forward it through TmpEnv.
• Pass {"globals": global_variables} when constructing TmpEnv in the runner.
• Add unit tests covering globals rendering and reserved-key behavior.

Show a summary per file

File	Description
tests/test_env_utils.py	Adds coverage for swap_env/TmpEnv with globals context and reserved-key filtering.
src/seclab_taskflow_agent/runner.py	Ensures task env-block rendering receives globals via TmpEnv(..., context=...).
src/seclab_taskflow_agent/env_utils.py	Implements optional template context in swap_env and plumbs it through TmpEnv.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 3/3 changed files
• Comments generated: 3

[Copilot]

Pull request overview

This PR fixes Jinja template rendering in task env: blocks so they can reference global variables (e.g. {{ globals.X }}), matching the behavior already supported in user_prompt rendering.

Changes:

• Extend swap_env() to accept an optional template context and pass it through TmpEnv.
• Update the runner to provide {"globals": global_variables} when rendering task env blocks.
• Add tests covering globals rendering, reserved key behavior, and TmpEnv rollback.

Show a summary per file

File	Description
src/seclab_taskflow_agent/env_utils.py	Adds context-aware Jinja rendering for env strings and forwards context through TmpEnv; adds rollback behavior on failure.
src/seclab_taskflow_agent/runner.py	Passes taskflow globals into TmpEnv so task env: blocks can render {{ globals.* }}.
tests/test_env_utils.py	New tests for swap_env()/TmpEnv with globals context and rollback behavior.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 3/3 changed files
• Comments generated: 1

[Copilot]

Catching jinja2.TemplateError and re-raising LookupError is a behavior change from the previous implementation (which returned the original string on template syntax/render errors). This can break existing configs that contain literal {{/{% sequences or other non-Jinja brace usage, and it also changes downstream behavior where callers treat LookupError as “missing env var” (e.g. some code deletes the entry on LookupError). If backward compatibility is required, consider preserving the old behavior for TemplateError (return s as-is) or introducing an explicit “strict” mode so invalid templates don’t get conflated with missing variables.