feat(maps): give displayed crystal balls a blue focal 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

Give intentionally displayed crystal balls a small blue focal light without turning every collectible crystal_ball into free passive carried illumination.

Keep the base item non-emitting. Establish display intent map-locally, using no_pick 1, a small radius, and 4060ff only where the object is genuinely scenery.

Evidence

The animated blue crystal_ball archetype is a pickable type-79 object with value 10 and no current radius or color. There are only two authored placements:

• Asteria world_4_47 at (11, 18), on the fortune teller's table;
• Marigold world_17_2_4 at (22, 9), beside the displayed power_crystal.

Adding an archetype-level radius would make either cheap collectible ball a passive carried light under Classic inventory semantics. Both current contexts instead look like fixed displays, so map-local ownership is safer—but only after confirming that making them unpickable does not remove intentional loot or interaction.

Scope

• Verify whether each of the two placements is intended as fixed display scenery or collectible loot.
• For each confirmed display, add map-local no_pick 1, radius 1, and 4060ff; leave any intentionally collectible placement non-emitting.
• Keep the shared crystal_ball archetype without a default radius so future collectible balls do not silently become inventory lights.
• Render the fortune-teller table and Marigold display in smooth and discrete Classic lighting, checking walls, nearby fixtures, and color overlap.
• Coordinate Marigold with feat(maps): give Wizards' Tower floors distinct ambient palettes #80 and feat(items): make power crystals provide a restrained carried light #95; do not stack adjacent focal sources without a deliberate composition.
• Preserve animation, value, type, name/plural, placement, scripts, NPC interaction, loot intent, and all unrelated gameplay fields.

Acceptance criteria

• The intended collectible-versus-display contract for both placements is documented.
• Confirmed displays use a small 4060ff focal light and cannot be picked up; any collectible placement remains non-emitting.
• The base archetype remains non-emitting and does not create a passive carried light.
• Asteria and Marigold displays remain readable without clipping, wall bleed, oversaturation, or accidental stacking with nearby emitters.
• No value, animation, NPC, script, loot, or gameplay behavior changes beyond the explicitly confirmed display ownership.
• The chore(maps): audit authored light-source colors #65 inventory, review records, 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. Both affected maps are currently byte-identical across release lines. Deliver compatible map-local changes through separate linked pull requests, with Classic 1.x owning rendered runtime evidence and main independently validating the authored mirror.

[zoeyrose]

Reconciliation update

The Classic 1.x implementation is updated in PR #120 at head 3fc252c1057ece20a6bdeec8ca5d1dcd73e5264a.

• The former main prerequisite feat(lighting): merge colored light content into main #66 is complete through merged PR feat(lighting): port reviewed light-source colors #124.
• The branch incorporates merged PR chore(lighting): remove committed render evidence #127 at b342d5632563730b12806414041cd4a4f575e07d.
• Issue chore(lighting): remove committed light-source evidence PNGs #126 and PR chore(lighting): remove committed render evidence #127 supersede the acceptance language requiring committed smooth/discrete PNGs, a manifest, or capture tooling. Optional renderer diagnostics stay ignored under build/.
• Both display instances remain fixed map-local radius-1 4060ff sources, while the collectible base archetype remains non-emitting.
• lights --check passes with 97 archetype sources, 4 artifact sources, 11,395 instances across 625 maps, and zero unreviewed sources.
• Full tools/validate.py passes all 119 tests and the aggregate content/archive checks.

PR #119 independently owns the adjacent Marigold power-crystal source; combining the two changes requires a semantic-digest refresh, not renewed committed render evidence. This update leaves the issue open for its separate release-line delivery decisions.

[zoeyrose]

Reconciled 1.x companion ready for maintainer merge

PR #120 has been rebuilt on the fresh post-#95 1.x tip and reconciled with the patch-only release policy.

• base: 1.x@371845c879955cb6910e2ac86b8ecf7ce7fca65e
• head: 08dbc332f0facaf00452037bd6f90ed1e277a553
• title/commit: fix(maps): light displayed crystal balls
• shape: exactly one commit and three changed paths
• GitHub state: open, non-draft, mergeable, and clean
• checks: Content validation, Conventional PR title, Syntax prototypes (Ubuntu), and Syntax prototypes (Windows) all passed on the exact head
• local validation: 131 tests plus lossless content, schema, catalog, contracts, syntax prototypes, licensing, runtime collection, both release archives, semantic audit, JSON parsing, title policy, and git diff --check passed
• inventory: 104 reviewed archetypes, 10 artifacts, 11,447 instances across 632 maps, 5,754 explicit colors, 5,807 intentional neutral emitters, zero unreviewed
• focused review: exactly two map objects each gain no_pick 1, radius 1, and 4060ff; the base archetype stays non-emitting; combined Marigold composition is reviewed; no capture metadata was restored

Merge order: squash-merge PR #120 first. After that merge, re-query both live tips before constructing the canonical main companion. Do not manually close #96 at this gate.

[zoeyrose]

1.x half merged

PR #120 was squash-merged as ca3733ef1892a973402d60df173d3a12e8195e75 from exact reviewed head 08dbc332f0facaf00452037bd6f90ed1e277a553.

Fresh post-merge tips:

• 1.x@ca3733ef1892a973402d60df173d3a12e8195e75
• main@81d71a575e0969ebe964893aa7c0ef9bfb63cb16

The canonical main companion will now be constructed and validated from that exact main tip. This issue remains open until the canonical companion is merged.

[github-actions]

🎉 This issue has been resolved in version 1.8.8 🎉

The release is available on:

• v1.8.8
• GitHub release

Your semantic-release bot 📦🚀