Compliance Templates — Slice 9: workflow reference-id substitution

[larsgeorge-db]

Parent PRD

#676

What to build

Let workflow authors reference a template field's stored value by its reference id — ${template.<ref>} — in approval-wizard or notification text, so governance values flow into consumer-facing steps without re-entry. Extend the existing substitution engine (common/workflow_executor.py::substitute_template, which already resolves ${entity.field} / ${context.attr} / ${step_results...}) to resolve the template. namespace against a product's stored compliance values (effective-value semantics: stored else current default).

See PRD user story 27.

Acceptance criteria

• ${template.<ref>} in approval-wizard / notification text resolves to the entity's stored value for that reference id
• Resolution uses effective-value semantics (stored value, else current default)
• Unknown/unset references degrade gracefully (consistent with existing substitution behavior)
• Resolution wired through the existing substitute_template engine, not a parallel path

Blocked by

• Blocked by Compliance Templates — Slice 3: defaults, hint text, reference id #708

User stories addressed

• User story 27