t27c gen: typed const with an enum literal (const D: Dir = .east;) loses its value #6255

Found by the t27b enums lane (PR #6254, Refs #6063, #6146).

Problem

t27c gen emits const D: Dir = .east; as const D: Dir;. The value is dropped, and Zig rejects the output with "variables must be initialized".

Evidence

The lane's scratch probe (/tmp/t27b-enums-scratch/t1.zig on the steward's Mac). Writing Dir.east in full is emitted correctly. t27b lowers both spellings.

Expected

The decl-literal .east is kept when the declared type is an enum.

Related

The second bug the lane hit, a reassigned var in a test block emitted as a const redeclaration, is already tracked in #5606 and #4847.

🤖 Generated with Claude Code

User Scenarios

• Given a t27 spec with a typed const using an enum shorthand literal (e.g., const D: Dir = .east;)
• When t27c gen compiles the spec
• Then the generated Zig code preserves the enum literal value (e.g., const D: Dir = .east;)

Requirements

• FR-001: t27c gen MUST preserve enum shorthand literals (e.g., .east) in typed const declarations when the declared type is an enum
• FR-002: t27c gen MUST emit valid Zig code that compiles without "variables must be initialized" errors

Success Criteria

• The command t27c gen spec.t27 exits with exit 0 for a spec containing const D: Dir = .east;
• The generated Zig file contains const D: Dir = .east; (not const D: Dir;)
• 1 test case passes for enum shorthand literal preservation in const declarations

Boundary

• bootstrap/t27c.py