chore(release): 0.7.6

[client-software-ci]

0.7.6 (2026-08-11)

Features

• RFC 0007/0008 support — step-level let bindings, wrap-hook step names, and template-declared
  extensions. A step's environments are entered with its step-level EXPR let bindings (RFC 0007),
  so environment variables and actions can reference them; RFC 0008 wrap hooks now resolve
  WrappedStep.Name; only the extensions a template declares are enabled; and Job.Name is
  seeded into the symbol table. (962e359)
• Support RFC extensions in environment templates (feat: Support RFC extensions in environment templates #213) (cc8d354)

Bug Fixes

• Require openjd-sessions >= 0.10.11 (dfa118d)
• openjd run printed a stack trace instead of a readable error message when an environment failed to enter (e.g. violating RFC 0008's "at most one wrap environment" rule)
• openjd run reported a misleading "Must exit Environment X first" error when an environment failed partway through entering (e.g. a bad environment variables expression)
• Step.Name was not available in a step's let bindings and step-environment actions (RFC 0007 EXPR)
• Defer adaptive chunk adjustment without a measurable sample (fix: Defer adaptive chunk adjustment without a measurable sample #232) (7091007)

[github-actions]

This release note states unconditionally that "A step's environments are entered with its step-level EXPR let bindings (RFC 0007)", but at the dependency floor declared in pyproject.toml that isn't true.

src/openjd/cli/_run/_local_session/_session_manager.py:443 reads the bindings defensively:

# getattr guard: requires an openjd-model with Step.let on the
# instantiated Job (openjd-model PR #318+); collapse to plain
# `step.let` once the version pin floor guarantees it.
step_let_bindings = getattr(step, "let", None)

but pyproject.toml pins openjd-model >= 0.9,< 0.12. On any resolved openjd-model older than the release that added Step.let, getattr returns None, so extra_let_bindings is never forwarded and step-level let silently no-ops — environment variables and actions that reference those bindings will fail to resolve (or resolve to nothing) with no error explaining why. A user installing openjd-cli==0.7.6 with an older-but-permitted openjd-model gets a release that advertises the feature and doesn't have it.

Note the sibling openjd-sessions floor was raised to >= 0.10.11 in this same release precisely to remove an equivalent version-skew guard; the openjd-model floor appears to have been left behind. Suggest either raising the openjd-model lower bound to the first version with Step.let (and dropping the getattr for a plain step.let), or qualifying this changelog bullet so the requirement is visible to users.