Copilot/configure shell scripts repo

.all-contributorsrc

@@ -1,50 +1,50 @@
 {
-	"projectName": "ai-block-theme-template",
-	"projectOwner": "lightspeedwp",
-	"repoType": "github",
-	"repoHost": "https://github.com",
-	"projectDescription": "Starter repository for WordPress block theme projects with AI support", // Brief description of the project
-	"projectWebsite": "https://lightspeedwp.agency", // Official project website
-	"license": "GPL-3.0-or-later", // Project license identifier
-	"files": [
-		"README.md" // Files where contributor information will be displayed
-	],
-	"imageSize": 100, // Size of contributor avatar images in pixels
-	"commit": false, // Whether to automatically commit changes (false for manual control)
-	"commitConvention": "conventional", // Commit message convention to follow
-	"contributors": [
-		// Array of project contributors
-		{
-			"login": "lightspeedwp", // GitHub username/organization handle
-			"name": "LightSpeedWP", // Display name for the contributor
-			"avatar_url": "https://avatars.githubusercontent.com/u/lightspeedwp?v=4", // GitHub avatar image URL
-			"profile": "https://github.com/lightspeedwp", // Link to contributor's profile
-			"contributions": [
-				// Types of contributions made to the project
-				"ideas", // Contributed ideas and concepts
-				"fundingFinding", // Helped find funding for the project
-				"projectManagement", // Managed project tasks and coordination
-				"business" // Handled business aspects and strategy
-			]
-		},
-		{
-			"login": "ashleyshaw", // GitHub username
-			"name": "Ashley Shaw", // Full name of the contributor
-			"avatar_url": "https://avatars.githubusercontent.com/u/ashleyshaw?v=4", // GitHub profile avatar
-			"profile": "https://github.com/ashleyshaw", // Link to GitHub profile
-			"contributions": [
-				// Comprehensive list of contribution types
-				"code", // Wrote code for the project
-				"design", // Created design elements and UI/UX
-				"doc", // Wrote or improved documentation
-				"ideas", // Contributed ideas and feedback
-				"infra", // Set up and maintained infrastructure
-				"maintenance", // Ongoing project maintenance
-				"projectManagement", // Managed project activities
-				"test" // Wrote tests and performed testing
-			]
-		}
-	],
-	"contributorsPerLine": 7, // Number of contributors to display per line in the README
-	"linkToUsage": true // Whether to include a link to all-contributors usage information
+    "projectName": "ai-block-theme-template",
+    "projectOwner": "lightspeedwp",
+    "repoType": "github",
+    "repoHost": "https://github.com",
+    "projectDescription": "Starter repository for WordPress block theme projects with AI support", // Brief description of the project
+    "projectWebsite": "https://lightspeedwp.agency", // Official project website
+    "license": "GPL-3.0-or-later", // Project license identifier
+    "files": [
+        "README.md" // Files where contributor information will be displayed
+    ],
+    "imageSize": 100, // Size of contributor avatar images in pixels
+    "commit": false, // Whether to automatically commit changes (false for manual control)
+    "commitConvention": "conventional", // Commit message convention to follow
+    "contributors": [
+        // Array of project contributors
+        {
+            "login": "lightspeedwp", // GitHub username/organization handle
+            "name": "LightSpeedWP", // Display name for the contributor
+            "avatar_url": "https://avatars.githubusercontent.com/u/lightspeedwp?v=4", // GitHub avatar image URL
+            "profile": "https://github.com/lightspeedwp", // Link to contributor's profile
+            "contributions": [
+                // Types of contributions made to the project
+                "ideas", // Contributed ideas and concepts
+                "fundingFinding", // Helped find funding for the project
+                "projectManagement", // Managed project tasks and coordination
+                "business" // Handled business aspects and strategy
+            ]
+        },
+        {
+            "login": "ashleyshaw", // GitHub username
+            "name": "Ashley Shaw", // Full name of the contributor
+            "avatar_url": "https://avatars.githubusercontent.com/u/ashleyshaw?v=4", // GitHub profile avatar
+            "profile": "https://github.com/ashleyshaw", // Link to GitHub profile
+            "contributions": [
+                // Comprehensive list of contribution types
+                "code", // Wrote code for the project
+                "design", // Created design elements and UI/UX
+                "doc", // Wrote or improved documentation
+                "ideas", // Contributed ideas and feedback
+                "infra", // Set up and maintained infrastructure
+                "maintenance", // Ongoing project maintenance
+                "projectManagement", // Managed project activities
+                "test" // Wrote tests and performed testing
+            ]
+        }
+    ],
+    "contributorsPerLine": 7, // Number of contributors to display per line in the README
+    "linkToUsage": true // Whether to include a link to all-contributors usage information
 }

.github/ISSUE_TEMPLATE/01-bug-report.md

@@ -67,7 +67,7 @@ Add any other context about the problem here.
 
 ### Fixed
 
-- 
+-
 
 ## Definition of Ready (DoR) Checklist
 
@@ -84,4 +84,4 @@ Add any other context about the problem here.
 - [ ] Tests updated/added to prevent regression
 - [ ] Documentation updated if needed
 - [ ] Changelog entry added
-- [ ] Fix verified in all affected environments
+- [ ] Fix verified in all affected environments

.github/ISSUE_TEMPLATE/02-feature-request.md

@@ -33,7 +33,7 @@ What type of automation would this be?
 - [ ] GitHub Actions workflow
 - [ ] Test harness
 - [ ] Documentation improvement
-- [ ] Other: _____
+- [ ] Other: **\_**
 
 ## Implementation considerations
 
@@ -74,4 +74,4 @@ Add any other context, mockups, or examples about the feature request here.
 - [ ] Documentation created/updated
 - [ ] Changelog entry added
 - [ ] Feature demonstrated and verified
-- [ ] Performance impact assessed (if applicable)
+- [ ] Performance impact assessed (if applicable)

.github/ISSUE_TEMPLATE/03-documentation.md

@@ -23,7 +23,7 @@ Describe what documentation needs to be created, updated, or improved.
 - [ ] Setup/installation instructions
 - [ ] Troubleshooting guides
 - [ ] API documentation
-- [ ] Other: _____
+- [ ] Other: **\_**
 
 ## Proposed Changes
 
@@ -42,7 +42,7 @@ Who is this documentation for?
 - [ ] DevOps engineers
 - [ ] Project maintainers
 - [ ] End users
-- [ ] Other: _____
+- [ ] Other: **\_**
 
 ## Additional Context
 
@@ -54,7 +54,7 @@ Add any other context about the documentation request here.
 
 ### Changed
 
-- 
+-
 
 ## Definition of Ready (DoR) Checklist
 
@@ -70,4 +70,4 @@ Add any other context about the documentation request here.
 - [ ] Clear, concise, and well-organized
 - [ ] Follows markdown style guidelines
 - [ ] Changelog entry added (if applicable)
-- [ ] Documentation merged and published
+- [ ] Documentation merged and published

.github/ISSUE_TEMPLATE/04-task.md

@@ -28,15 +28,15 @@ Why does this task need to be done? What value does it provide?
 - [ ] Maintenance
 - [ ] Infrastructure
 - [ ] Testing
-- [ ] Other: _____
+- [ ] Other: **\_**
 
 ## Requirements
 
 List specific requirements for completing this task.
 
-1. 
-2. 
-3. 
+1.
+2.
+3.
 
 ## Success Criteria
 
@@ -52,7 +52,7 @@ Links to documentation, related issues, or context that might be helpful.
 
 ### Changed
 
-- 
+-
 
 ## Definition of Ready (DoR) Checklist
 
@@ -69,4 +69,4 @@ Links to documentation, related issues, or context that might be helpful.
 - [ ] Tests added/updated as needed
 - [ ] Documentation updated (if applicable)
 - [ ] Changelog entry added (if applicable)
-- [ ] Changes merged and deployed
+- [ ] Changes merged and deployed

.github/ISSUE_TEMPLATE/05-refactoring.md

@@ -37,7 +37,7 @@ What benefits will this refactoring provide?
 - [ ] Reduced complexity
 - [ ] Enhanced readability
 - [ ] Easier testing
-- [ ] Other: _____
+- [ ] Other: **\_**
 
 ## Risks and Challenges
 
@@ -63,4 +63,4 @@ Any other context, code examples, or references that might help.
 - [ ] Code coverage maintained or improved
 - [ ] Documentation updated (if needed)
 - [ ] Code review completed
-- [ ] Performance impact verified (if applicable)
+- [ ] Performance impact verified (if applicable)

.github/ISSUE_TEMPLATE/06-integration.md

@@ -20,7 +20,7 @@ Describe the integration that's affected:
 - [ ] CI/CD system
 - [ ] Deployment platform
 - [ ] Authentication system
-- [ ] Other: _____
+- [ ] Other: **\_**
 
 ## Current Behavior
 
@@ -39,9 +39,9 @@ What should be happening instead?
 
 ## Steps to Reproduce
 
-1. 
-2. 
-3. 
+1.
+2.
+3.
 
 ## Logs or Error Messages
 
@@ -59,7 +59,7 @@ If you have ideas about how to fix the integration, please share them.
 
 ### Fixed
 
-- 
+-
 
 ## Definition of Ready (DoR) Checklist
 
@@ -76,4 +76,4 @@ If you have ideas about how to fix the integration, please share them.
 - [ ] Documentation updated (if applicable)
 - [ ] Changelog entry added
 - [ ] Integration verified in all relevant environments
-- [ ] Security implications reviewed (if applicable)
+- [ ] Security implications reviewed (if applicable)

.github/ISSUE_TEMPLATE/config.yml

@@ -1,11 +1,11 @@
 blank_issues_enabled: false
 contact_links:
-  - name: ❓ Questions & Discussions
-    url: https://github.com/lightspeedwp/scripts/discussions
-    about: Ask questions, discuss best practices, or share ideas about our automation scripts
-  - name: 📚 Documentation
-    url: https://github.com/lightspeedwp/scripts/tree/main/docs
-    about: Check our documentation for guides and examples
-  - name: 📝 Contribution Guide
-    url: https://github.com/lightspeedwp/scripts/blob/main/CONTRIBUTING.md
-    about: Learn how to contribute to our automation scripts
+    - name: ❓ Questions & Discussions
+      url: https://github.com/lightspeedwp/scripts/discussions
+      about: Ask questions, discuss best practices, or share ideas about our automation scripts
+    - name: 📚 Documentation
+      url: https://github.com/lightspeedwp/scripts/tree/main/docs
+      about: Check our documentation for guides and examples
+    - name: 📝 Contribution Guide
+      url: https://github.com/lightspeedwp/scripts/blob/main/CONTRIBUTING.md
+      about: Learn how to contribute to our automation scripts

.github/PROJECT_META.client-delivery.md

@@ -4,11 +4,11 @@
 
 ## Quick Start
 
-1) **Create Project** → Name `Client – {ClientName}`; Description with scope + contract link.
-2) **Add fields**: Status (Backlog, **To‑do**, In progress, In review, In QA, Done), Issue Type (Epic, Story, Task, Bug, Chore, Design, Research), Priority, Area, Theme, **Size (single‑select)**, Start Date, Deadline, **Milestone (iteration)**, Environment, Parent Issue, Sub‑issues Progress, Time (hours). Optional: Iteration.
-3) **Automations**: Auto‑add → Backlog; On Assignee → In progress; On linked PR → In review; On `status:needs-qa` → In QA; On close/merge → Done.
-4) **Pin views**: Board — Team Flow (group by Assignee), Backlog — Table, **QA Gate**, **UAT (Client)**, Roadmap, Blocked, Epics (Tracking) — Table/Roadmap.
-5) **Intake hygiene**: Create **Intake** view (`Status = Backlog` AND missing Assignee/Priority/Issue Type) and clear it weekly.
+1. **Create Project** → Name `Client – {ClientName}`; Description with scope + contract link.
+2. **Add fields**: Status (Backlog, **To‑do**, In progress, In review, In QA, Done), Issue Type (Epic, Story, Task, Bug, Chore, Design, Research), Priority, Area, Theme, **Size (single‑select)**, Start Date, Deadline, **Milestone (iteration)**, Environment, Parent Issue, Sub‑issues Progress, Time (hours). Optional: Iteration.
+3. **Automations**: Auto‑add → Backlog; On Assignee → In progress; On linked PR → In review; On `status:needs-qa` → In QA; On close/merge → Done.
+4. **Pin views**: Board — Team Flow (group by Assignee), Backlog — Table, **QA Gate**, **UAT (Client)**, Roadmap, Blocked, Epics (Tracking) — Table/Roadmap.
+5. **Intake hygiene**: Create **Intake** view (`Status = Backlog` AND missing Assignee/Priority/Issue Type) and clear it weekly.
 
 ## Status
 

.github/PROJECT_META.md

@@ -11,9 +11,9 @@ Automatically **add issues/PRs to the org Project** and keep Project **fields in
 - **Triggers** on issue and PR events.
 - **Adds the item** to the org Project using `LS_PROJECT_URL`.
 - **Derives** and writes Project fields:
-  - **Status** from `status:*` labels (closed/merged → `Done`; default **Backlog**).
-  - **Priority** from `priority:*` labels.
-  - **Type** from **PR head branch** (see PR labels).
+    - **Status** from `status:*` labels (closed/merged → `Done`; default **Backlog**).
+    - **Priority** from `priority:*` labels.
+    - **Type** from **PR head branch** (see PR labels).
 
 ## Setup requirements
 

.github/PROJECT_META.product-development.md

@@ -4,11 +4,11 @@
 
 ## Quick Start
 
-1) **Create Project** → Name `Product – {ProductName}`; Description with objective + README/roadmap link.
-2) **Add fields**: Status (Backlog, **Ready**, In progress, In review, In QA, Done), Issue Type (Epic, Feature, Story, Task, Bug, Refactor, Design, Research, Chore), Priority, **Milestone/Release (vX.Y.Z)**, Area, Theme, **Size (single‑select)**, Start Date, Deadline, Environment, Parent Epic, Sub‑issues Progress, Time (hours). Optional: Iteration (Sprint).
-3) **Automations**: Auto‑add → Backlog; On Assignee → In progress; On linked PR → In review; On `status:needs-qa` → In QA; On close/merge → Done.
-4) **Release scaffolding**: Create Milestone `vX.Y.Z`; add scoped Features/Stories; pin **Release Gate — vX.Y.Z** view.
-5) **Pin views**: Release Gate, Tech Debt, Roadmap, Backlog — Table, Epics — Table/Roadmap/Board, Epic drill‑down (group by Parent Epic).
+1. **Create Project** → Name `Product – {ProductName}`; Description with objective + README/roadmap link.
+2. **Add fields**: Status (Backlog, **Ready**, In progress, In review, In QA, Done), Issue Type (Epic, Feature, Story, Task, Bug, Refactor, Design, Research, Chore), Priority, **Milestone/Release (vX.Y.Z)**, Area, Theme, **Size (single‑select)**, Start Date, Deadline, Environment, Parent Epic, Sub‑issues Progress, Time (hours). Optional: Iteration (Sprint).
+3. **Automations**: Auto‑add → Backlog; On Assignee → In progress; On linked PR → In review; On `status:needs-qa` → In QA; On close/merge → Done.
+4. **Release scaffolding**: Create Milestone `vX.Y.Z`; add scoped Features/Stories; pin **Release Gate — vX.Y.Z** view.
+5. **Pin views**: Release Gate, Tech Debt, Roadmap, Backlog — Table, Epics — Table/Roadmap/Board, Epic drill‑down (group by Parent Epic).
 
 ## Status
 

.github/PR_LABELS.md

@@ -8,11 +8,11 @@ Provide high‑signal, automated **PR labels** for review routing, release hygie
 
 ## How labels are applied
 
-1) **Paths → labels** via `.github/labeler.yml`:
-   - `area:ci`, `area:dependencies`, `area:block-editor`, `area:theme`, `area:integration` …
-   - `lang:php`, `lang:javascript`, `lang:css`, `lang:md` …
-2) **Branch prefixes → status** (on PR open):
-   - `feat/`, `fix/`, `docs/`, `chore/`, `build/` → add **`status:needs-review`** by default.
+1. **Paths → labels** via `.github/labeler.yml`:
+    - `area:ci`, `area:dependencies`, `area:block-editor`, `area:theme`, `area:integration` …
+    - `lang:php`, `lang:javascript`, `lang:css`, `lang:md` …
+2. **Branch prefixes → status** (on PR open):
+    - `feat/`, `fix/`, `docs/`, `chore/`, `build/` → add **`status:needs-review`** by default.
 
 ### Optional branch→type mapping (for Projects)
 

.github/PULL_REQUEST_TEMPLATES/pr_bug.md

@@ -1,10 +1,8 @@
 ---
-
-name: "Bugfix PR"  
-about: "Fix a defect/regression with clear repro, fix, and verification"  
-title: "fix: {short summary}"  
-labels: ["status:needs-review"]  
-
+name: 'Bugfix PR'
+about: 'Fix a defect/regression with clear repro, fix, and verification'
+title: 'fix: {short summary}'
+labels: ['status:needs-review']
 ---
 
 # Bugfix Pull Request

.github/PULL_REQUEST_TEMPLATES/pr_chore.md

@@ -1,18 +1,15 @@
 ---
-
-name: "Chore PR"  
-about: "Repo hygiene: configs, scripts, formatting — no behaviour change"  
-title: "chore: {scope}"  
-labels: ["status:needs-review"]  
-
+name: 'Chore PR'
+about: 'Repo hygiene: configs, scripts, formatting — no behaviour change'
+title: 'chore: {scope}'
+labels: ['status:needs-review']
 ---
 
 # Chore Pull Request
 
 > This repository enforces changelog, release, and label automation for all PRs and issues.  
 > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/main/AUTOMATION_GOVERNANCE.md) for required rules.
 
-
 ## Linked issues
 
 <!--
@@ -77,7 +74,6 @@ If no user-facing changelog entry is needed, apply the skip-changelog label to t
 
 ---
 
-
 ### Checklist (Global DoD / PR)
 
 - [ ] All AC met and demonstrated