fix: bare dictionary subscript on action output compiled to Property aggrandizement

[BTForIT]

Bug

A bare dictionary subscript on an action-output variable compiles to the wrong aggrandizement type:

#include 'actions/scripting'
@resp = "..."
const respDict = getDictionary(@resp)

@summary = respDict['summary']        // BUG: WFPropertyVariableAggrandizement → empty at runtime
const s = "{respDict['summary']}"     // OK:  WFDictionaryValueVariableAggrandizement

variableValue() only emits WFDictionaryValueVariableAggrandizement when the referenced variable's value type is Dict. A variable holding an action's output has value type Action, so the subscript falls through to WFPropertyVariableAggrandizement — which Shortcuts resolves to an empty value at runtime (a dictionary has no such content-item property). The identical subscript inside string interpolation was already correct because makeAggrandizement() resolves Action references through the action definition's outputType.

Hit in production: a shortcut that read Resp['status'] after a downloadURL() POST branched to its failure alert on every successful run.

Fix

shortcutgen.go variableValue(): when the reference's value type is Action, resolve it to the action definition's outputType before the Dict check — the same resolution makeAggrandizement() already performs. +10 lines.

Verification

• New fixture tests/dictionary-action-output.cherri (bare + inline subscript on getDictionary() output). Before: bare case emitted 1 WFPropertyVariableAggrandizement. After: both emit WFDictionaryValueVariableAggrandizement (2/0).
• Differential compile of every existing tests/*.cherri fixture with baseline vs fixed binaries: zero regressions; all byte-level differences reproduce between two baseline runs as well (UUID nondeterminism only).
• On-device: the runtime behavior of both aggrandizement types was confirmed on a real device — the Property form yields an empty value on a dictionary, the DictionaryKey form resolves the key. (The affected production shortcut was patched by moving the subscripts into string interpolation, which compiles to the DictionaryKey form.)
• go test -vet=off ./... fails identically on the base branch (Duplicate enumeration 'backgroundSound' — the test harness's resetParser() doesn't clear enum state between fixtures, and go vet separately flags a pre-existing unused slices.Delete result in actions_std.go:817). Neither is introduced or affected by this change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PmFsHCZ4S5KAiUCu4uZAtH