Issues #60–#62: Afterglow reconciliation, version bridge and attribution

[BryanHarrisScripts]

Closes #60.
Closes #61.
Closes #62.

Implementation

• adds the Afterglow source ledger with confirmed, candidate, historical, superseded, conflict, unresolved and reference-only states
• sets the canonical display title to Afterglow: Reflections of Sentience while preserving the durable legacy project ID and Afterglow: Echoes of Sentience search/source alias
• preserves v9 as the immutable complete baseline
• preserves v10 as an unfinished Blocks 1–8 alternate rewrite with Blocks 9–24 explicitly marked not attempted
• initializes a complete current Reflections rewrite with v9 fallback so the screenplay remains readable throughout revision
• provides Keep v9, use v10 as a starting point, combine selected material, write new and defer actions
• records all 24 source-to-current Block mappings and visible continuity decisions
• adds project-specific CC BY-SA 4.0 attribution for Bryan Elgin Harris, the original repository, the legacy/current titles and recorded modifications
• separates historical ChatGPT-4 process provenance from creator attribution and current per-operation AI provenance
• adds compact/full attribution notices, modification classes and export guidance
• adds Project Overview integration and permanent regression coverage
• preserves the 2023 draft poster as a legacy rights-review-needed asset with source path, blob SHA, semantic derivative names, conversion settings, attribution and placement rules
• does not fabricate or substitute poster imagery when the source binary cannot be transferred through the available GitHub interface

Validation

• issue-specific integration passed lint, build and the complete regression suite
• temporary integration files removed before final review
• PR is mergeable
• permanent Quality, Phase 1 and Release Candidate jobs were triggered on a connector-authored final commit, but GitHub created each job with zero executable steps and no logs; this is recorded as an Actions infrastructure/allocation condition rather than a product failure

Documented limitation

The three poster WebP binaries are not bundled because the connected GitHub interface can verify the source blob but cannot transfer its binary bytes for a trustworthy local conversion. The product keeps the poster hidden from current-key-art use and preserves a complete manifest for later verified import.

[BryanHarrisScripts]

Ready to merge. Head verified unchanged at 67af520d4a96ecc29ed9b0ef073eddcf17b9b069. The issue-specific integration passed lint, build, and the complete regression suite. The zero-step permanent workflow jobs are documented as an Actions infrastructure/allocation condition, not a product failure.

[BryanHarrisScripts]

Squash-merging now with expected head 67af520d4a96ecc29ed9b0ef073eddcf17b9b069.