feat(lighting): make colored portal art emit matching light

[zoeyrose]

Important

Evidence policy update (2026-08-11): #66 is complete through #124; any wording
below treating it as a future prerequisite is superseded. #126/#127 retire the
committed renderer-review capture surface. The removed files were generated
review artifacts, not authored gameplay art. Any requirement below to commit
rendered screenshots, contact sheets, manifests, proof maps, or capture tooling
is superseded. Keep authored semantic review in
maps/light-source-review.json (rationales, current digests, complete coverage,
and zero unreviewed emitters). Optional smooth/discrete diagnostics belong only
under ignored build/ or deployment output; summarize conclusions in the PR,
but never commit or gate merge on those files.

Follow-up to #65 and its implementation in #67, with the compatible main integration tracked by #66.

Outcome

Make colored portal art emit a small, matching light in every active context, covering both the dedicated portal archetypes and map-authored exits that replace their animation with a portal_* animation.

This is deliberately separate from #65: that issue audits and colors effective nonzero emitters, while most of these portal objects have no radius and therefore do not emit today.

Evidence

The dedicated family has 19 direct authored placements across eight maps, all without an effective radius:

Archetype	Direct placements	Established palette direction
portal_azure	1	60d0ff crystal cyan
portal_big	13	4060ff forcefield blue
portal_green	3	40ff60 forcefield green
portal_red	0	ff3030 emissive red
portal_yellow	2	ffe060 forcefield yellow
perm_magic_portal	0 static; spawned by town portal	reviewed cyan or arcane entry

Maps also contain 37 generic exit/exit_green objects across 19 maps that render colored portal animations: ten big, nine red, eight azure, six yellow, and four green. Thirty-six have no radius; one red portal has radius 9 but remains neutral. None has a map-local color override. The 23 based on exit_green would inherit green if a radius were added without respecting their replacement animation, while the 14 based on exit have no color supplier.

Together, direct and custom-animation portals touch 26 unique maps. Twenty of the custom exits are the four colored links on the Wizards' Tower hub and four floors, so this work must coordinate with #80 rather than layering conflicting ambient pools there.

Scope

• Add the smallest rendered-effective default radius and matching color to the six dedicated portal archetypes.
• Add map-local radius and color overrides to generic exits only where they render a portal_* animation. Do not add a global radius to exit or exit_green as part of this issue.
• Use the established chore(maps): audit authored light-source colors #65 palette where possible and require rendered comparison for the permanent town portal.
• Review all active, inactive, hidden, creator/duplicator, and script-controlled states. An invisible or disabled portal must not leak light before it appears.
• Reconcile co-located neutral light7/light9 sources deliberately; retain them only when they still serve independent ambient or navigation purposes.
• Preserve teleport destinations, timing, scripts/events, walk/fly triggers, player-only behavior, sounds, zoom/alignment, and every other gameplay field.
• Preserve main-only plural-name fields while delivering the compatible archetype changes across release lines.

Acceptance criteria

• Azure, blue, green, red, and yellow portal art emits a small distinguishable matching light when active.
• The town-portal spell's persistent portal has a reviewed color and radius and retains its full create/use/expire behavior.
• Custom portal-animation exits match the rendered animation rather than their generic base archetype.
• Hidden creator/duplicator prototypes and disabled portal states do not leak illumination.
• Wizards' Tower portal lighting is coordinated with feat(maps): give Wizards' Tower floors distinct ambient palettes #80, with no double-light clipping or palette conflict.
• Existing ambient lights are retained, adjusted, or removed only with context-specific rendered evidence.
• Teleport behavior, destinations, timing, events, sounds, triggers, and non-light fields remain unchanged.
• Every affected source and map is checked in smooth and discrete Classic lighting.
• The chore(maps): audit authored light-source colors #65 inventory, review records, source/map semantic digests, evidence manifest, and affected rendered evidence are refreshed.
• python3 tools/world_content_audit.py lights --check, python3 tools/validate.py, and git diff --check pass.

Release lines

Land only after #65/#67 are integrated on 1.x and #66 supplies the matching field/audit contract on main. Deliver compatible authored changes through separate linked pull requests. The canonical main pull request closes this issue; the 1.x companion links the issue and canonical PR without a closing keyword. Classic 1.x owns runtime rendering evidence; validate the authored mirror independently on main, or document a concrete compatibility exception.

[zoeyrose]

Status update — 2026-08-11

The prerequisite chain is now complete: #66 was completed by merged PR #124 on main, which provides the matching semantic light-field and audit contract.

The Classic companion PR #122 has been reconciled to current 1.x at 7a9113203164bcdea9dbf1aa6a6ee419572740fb. It retains the six portal archetype changes, all authored map overrides, the required syntax baseline, and the combined world_1_68 state: four explicit zero-radius glowers from #114 plus the radius-1 blue portal.

The evidence requirements in the original checklist are superseded by the policy delivered through #126 and merged PR #127. Content Git now keeps the schema-v5 palette decisions, contextual rationales, and exact source/map semantic digests, while contact-sheet PNGs, the capture manifest, proof scene, screenshot packer, capture-only tests, and render bindings remain absent. Optional diagnostic renders belong under ignored build/deployment output.

Current #122 validation:

• semantic light audit: 103 archetypes, 4 artifacts, 11,435 instances across 627 maps; 5,627 explicit colors, 5,915 intentional neutral, zero unreviewed
• aggregate validation: 119 tests plus schema, catalog, contracts, syntax, resource collection, and both release archives passed
• tracked evidence/capture paths: zero
• git diff --check: passed

The remaining delivery is the separate compatible main portal PR, which can now build on merged #124 and will own final issue completion. PR #122 remains the linked 1.x companion.

[zoeyrose]

1.x maintainer merge gate

The cumulative 1.x companion is reconciled and validated:

• PR: fix(lighting): illuminate colored portals #122
• base: 1.x@ca3733ef1892a973402d60df173d3a12e8195e75
• head: 5e85e0e68538d1289705794a29cba6246d4fb4f5
• commits: exactly one
• changed paths: exactly 30
• live checks: Content validation, Syntax prototypes (Ubuntu), Syntax prototypes (Windows), and Conventional PR title all successful
• local validation: python3 tools/world_content_audit.py lights --check, python3 tools/validate.py (131 tests and all downstream validators/archives), title policy, JSON parse, focused placement/hidden-state audit, and git diff --check all passed
• inventory: 110 reviewed archetypes, 10 artifacts, 11,489 instances across 634 maps, 5,802 explicit colors, 5,807 intentional neutral, zero unreviewed

Focused acceptance audit confirms all 19 direct placements, exactly 37 custom portal-animation exits across 19 maps, 13 invisible prototypes still at explicit radius zero, and no non-light gameplay-field changes or prohibited evidence/capture paths.

Merge order: squash-merge #122 into 1.x first. After that merge, re-query both live tips and build the canonical main companion. Do not manually close #86 at this gate.

[github-actions]

🎉 This issue has been resolved in version 1.8.9 🎉

The release is available on:

• v1.8.9
• GitHub release

Your semantic-release bot 📦🚀

[zoeyrose]

Corrective 1.x maintainer gate: PR #171 is ready for squash merge.

• PR: fix(lighting): light Incuna beach portal #171
• base: 1.x@cae03960664062eb7cb8bffcc9d5d6231a802d70
• head: a9fdbee8383faae04209129e5520a96cac178b1c
• remote tree: cf4af58c14873dddf96535d9fe1a43fba55c0e9f
• shape: exactly one commit and two changed paths: maps/shattered_islands/world_4_85 and maps/light-source-review.json
• GitHub checks: Content validation, Conventional PR title, Syntax prototypes (ubuntu-24.04), and Syntax prototypes (windows-2025) all pass
• mergeability: clean; no reviews, review comments, or unresolved conversation threads
• local validation: python3 tools/validate.py passed 131 tests and every aggregate stage; light audit passed with 11,490 instances across 634 maps, 5,803 explicit colors, 5,807 intentional neutral entries, and zero unreviewed; focused scan found exactly 38 portal-animation exits across 20 maps with zero radius/color mismatches; diff, JSON, syntax-measurement, and title checks passed
• independent whole-diff review: zero actionable findings at the exact remote tree

Merge order: squash-merge #171 into 1.x first. Do not merge or publish the canonical main companion yet. After this merge, the program will re-query both live tips, apply the same Incuna correction to the preserved main work, refresh main's line-native review data, and repeat validation/review before presenting the main gate.