review · segments

Lanyard mention audit for enmbook rename

pi 84 events 1 segments

segment 1 of 1

Classify every 'lanyard' occurrence in the enmbook repo

Done

The agent confirmed Solo context, read the audit spec from scratchpad 779, locked todo 415, and performed a comprehensive case-insensitive grep for 'lanyard' across the defined scope (excluding vendor, node_modules, .git, storage, public/build, .claude). It found 64 occurrences, verified that user-facing runtime strings (Category D) are zero (already fixed in commit 3bd8358), and categorized the rest into A (working name/brand prose, 11), B (visual motif, 37), C (identifiers/config refs, 13), and E (placeholder domains, 3). Findings were written to scratchpad 781 and todo 415 was marked READY FOR REVIEW.

outcome

Findings scratchpad 781 contains the full inventory with summary, per-directory counts, and category breakdown; todo 415 is commented READY FOR REVIEW.

next steps

—

key decisions

Reserved slug 'lanyard' in ReservedSlugs.php is intentional squat protection and should stay.
All lanyard-mark visual motif usage (Category B) is kept as-is.
Category D is clean; docs/19-content-plan.md:479 is stale prose only.
13 doc lines reference config/lanyard.php or config('lanyard.*') but the shipped file is config/enmbook.php — this mismatch needs a decision.

open questions

Should the lanyard-mark component identifier be renamed?
How to handle docs/00-readme.md historical working-name callout?
When to sweep doc config-key references vs. switch placeholder domains?

3 weeks ago → 3 weeks ago