chore: convert ls-starter-theme scaffold into production ls-theme repo

[Copilot]

Replaces all {{PLACEHOLDER}} tokens with final values and updates all "starter/template" wording to reflect this is now the live lightspeedwp/ls-theme production repository.

Token replacements

All nine tokens replaced across 17 files:

Token	Value
{{THEME_NAME}}	LightSpeed Theme
{{THEME_SLUG}} / {{TEXT_DOMAIN}}	ls-theme
{{THEME_URI}} / {{AUTHOR_URI}}	https://lightspeedwp.agency/
{{AUTHOR_NAME}}	LightSpeed
{{GITHUB_ORG}} / {{REPO_NAME}}	lightspeedwp / ls-theme
{{THEME_DESCRIPTION}}	Full description string

Bug fix — invalid PHP function names

{{TEXT_DOMAIN}} expands to ls-theme, which produces hyphenated PHP identifiers — invalid syntax. Function names corrected to use underscores:

// Before (invalid PHP)
function ls-theme_setup() { … }
add_action( 'after_setup_theme', 'ls-theme_setup' );

// After
function ls_theme_setup() { … }
add_action( 'after_setup_theme', 'ls_theme_setup' );

Text domain strings (e.g. load_theme_textdomain( 'ls-theme', … )) remain hyphenated — correct per WordPress convention.

Wording updates

• README.md — title, intro, and Quick Start rewritten for the real repo; placeholder token table removed.
• AGENTS.md — "Repo Purpose" rewritten; placeholder table replaced with an identity values table; AI rule 15/16 updated.
• .github/copilot-instructions.md — "Repo Overview" updated; "Placeholder Tokens" section replaced with a "Theme Identity" table.
• CHANGELOG.md — initial release note de-"starter"-ified; unreleased entry added for this change.
• .github/tasks/task-list.md — setup tasks marked complete.

Preserved intentionally

Meta-references to {{TOKEN}} syntax in prompt files (.github/prompts/), the block-theme-audit skill, and the theme-utils.mjs detector — these describe/detect the placeholder pattern itself and must not be replaced.

Remaining manual actions

• screenshot.png — needs creating (1200×900).
• CHANGELOG.md [0.1.0] date — fill in when tagging the first release.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• schemas.wp.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node theme-utils.mjs validate-schema (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

You are working inside a new GitHub repository created from lightspeedwp/ls-starter-theme.

Your task is to convert this starter into LightSpeed’s new WordPress block theme repository.

Use these exact replacement values across the entire repository:

• {{THEME_NAME}} = LightSpeed Theme
• {{THEME_SLUG}} = ls-theme
• {{TEXT_DOMAIN}} = ls-theme
• {{THEME_URI}} = https://lightspeedwp.agency/
• {{AUTHOR_NAME}} = LightSpeed
• {{AUTHOR_URI}} = https://lightspeedwp.agency/
• {{THEME_DESCRIPTION}} = LightSpeed Theme is a custom WordPress block theme built by LightSpeed for fast, accessible, maintainable websites using the WordPress Site Editor and block editor.
• {{REPO_NAME}} = ls-theme
• {{GITHUB_ORG}} = lightspeedwp

Instructions:

1. Scan the full repository for any remaining mustache-style placeholders using {{...}}.
2. Replace every placeholder everywhere it appears, including:
   • file contents
   • markdown docs
   • config files
   • JSON files
   • CSS header metadata
   • composer metadata
   • package metadata
   • Code owners and GitHub AI files
3. Pay special attention to these files because they already contain placeholders:
   • style.css
   • README.md
   • readme.txt
   • package.json
   • composer.json
   • AGENTS.md
   • .github/copilot-instructions.md
   • CODEOWNERS
4. Keep {{TEXT_DOMAIN}} and {{THEME_SLUG}} aligned as ls-theme everywhere.
5. Update all human-readable copy that still describes this repo as a “starter repo” when that wording no longer makes sense for the real theme repository.
   • Change the wording so the repo reads as LightSpeed’s actual theme repo, not a reusable scaffold.
   • Keep the AI workflow structure, validation tooling, and documentation structure intact unless something is clearly scaffold-only.
6. Update headings and descriptions so they refer to:
   • the theme as LightSpeed Theme
   • the repo as ls-theme
   • the company as LightSpeed
   • the company site as https://lightspeedwp.agency/
7. Keep the existing block theme structure and tooling unless a reference is clearly starter-only and should be rewritten.
8. Do not rename folders unless required.
9. Do not add new dependencies unless necessary.
10. Preserve WordPress block theme best practices:
    • theme.json first
    • minimal PHP
    • accessibility
    • secure escaping and sanitisation
11. After replacements are complete, do a final pass to check for:
    • any remaining {{
    • any “starter repo” wording that should now say “theme repo” or “WordPress block theme”
    • any mismatch between ls-theme, LightSpeed Theme, and lightspeedwp/ls-theme
12. Then provide:
    • a concise summary of what changed
    • a list of files updated
    • a list of any values that still need manual confirmation

Specific file expectations:

• style.css

  • set the theme header fields to the final values above
  • keep version at 0.1.0 unless another version is already intended

• package.json

  • set "name" to ls-theme
  • set "description" to the final theme description

• composer.json

  • set "name" to lightspeedwp/ls-theme
  • set "description" to the final theme description
  • set author name and homepage correctly

• CODEOWNERS

  • update the comment header to # lightspeedwp/ls-theme CODEOWNERS
  • keep the existing team owner unless there is a clear reason not to

• README.md

  • rewrite the title and intro for the actual theme repo
  • remove unnecessary scaffold wording
  • keep the repo map, commands, and workflow sections if still useful

• AGENTS.md

  • rewrite repo-purpose language so it describes the actual LightSpeed theme repo
  • keep the AI workflow rules and WordPress standards guidance

• .github/copilot-instructions.md

  • update repo description to reflect the real theme repo, not a starter
  • keep references to AGENTS and the .github/ structure

• readme.txt

  • fill all placeholders
  • keep it lightweight and consistent with the theme identity

When finished, output the remaining unresolved items, if any.

[Copilot]

Copilot wasn't able to review any files in this pull request.