Quote long 0x hex literals in GitHub workflow YAML to fix parsing errors

[MontrealAI]

Motivation

• A long 0x… literal was being parsed by YAML as a hex integer and rejected as "too large", causing an "Invalid workflow file" failure for CI and demo workflows.
• The intent is to make these values explicitly strings so the workflow YAML parses cleanly without changing runtime behaviour.
• Fixing the YAML typing prevents GitHub Actions from rejecting workflow files while preserving existing env values.
• Keep changes minimal and scoped to quoting literals only so assertions and workflow semantics remain unchanged.

Description

• Wrap long 0x... literals in quotes in workflow env blocks so YAML treats them as strings instead of integers.
• Files modified: .github/workflows/ci.yml, .github/workflows/demo-aurora.yml, .github/workflows/demo-asi-global.yml, .github/workflows/demo-asi-takeoff.yml, .github/workflows/demo-zenith-hypernova.yml, .github/workflows/demo-zenith-sapience-celestial-archon.yml, .github/workflows/demo-zenith-sapience-initiative.yml, .github/workflows/demo-zenith-sapience-omnidominion.yml, and .github/workflows/demo-zenith-sapience-planetary-os.yml.
• No logic, secrets, sanity checks, or assertions were loosened; only YAML quoting was added to prevent mis-typing.

Testing

• Ran a YAML parse check with Python (yaml.safe_load) across .github/workflows/*.yml which succeeded and printed "Workflow YAML parse ok".
• Executed npm run ci:sync-contexts -- --check, npm run ci:verify-contexts, npm run ci:verify-companion-contexts, and npm run ci:verify-summary-needs, and all completed successfully.
• Verified the ci/required-contexts.json manifest and the CI summary needs remain in sync with ci.yml.
• Confirmed no workflow parsing errors were detected locally after the changes.

---

Codex Task