Add missing .github CI/CD workflow and issue/PR templates

[Copilot]

The .github/ directory referenced in the README architecture was entirely absent — no CI workflow, no issue templates, no PR template — despite CONTRIBUTING.md stating "CI/CD will run automatically."

Description

• .github/workflows/ci.yml: CI pipeline on push/PR to main — installs deps, runs eslint, builds with vite. GitHub token scoped to contents: read.
• .github/ISSUE_TEMPLATE/bug_report.md: Bug report template matching spec in CONTRIBUTING.md.
• .github/ISSUE_TEMPLATE/feature_request.md: Feature request template matching spec in CONTRIBUTING.md.
• .github/pull_request_template.md: PR template matching spec in CONTRIBUTING.md.

Type of Change

• New feature
• Bug fix
• Breaking change
• Documentation update

Testing

CI workflow validated locally: npm run lint and npm run build both pass from frontend/. CodeQL scan returned zero alerts after adding explicit permissions: contents: read to the workflow job.

Screenshots (if applicable)

N/A

Checklist

• Code follows project style guidelines
• Self-reviewed my code
• Commented complex areas
• Updated documentation
• No new warnings
• Added tests (if applicable)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[ecc-tools]

Analyzing 200 commits...

[ecc-tools]

✅ Analysis Complete

Generated skill from 32 commits | Confidence: 75%

🔗 View Pull Request #11

Repository Profile

Attribute	Value
Language	TypeScript
Framework	Not detected
Commit Convention	freeform
Test Directory	separate

Detected Workflows (5)

Workflow	Description
feature-development	Standard feature implementation workflow
react-component-bug-fixing	Fix TypeScript/ESLint errors and type safety issues in React components
feature-documentation-workflow	Add new features with comprehensive documentation and README updates
mcp-integration-expansion	Add new MCP server integrations to expand platform capabilities
collaborative-pr-workflow	Pull request workflow with co-authored commits and iterative improvements

Generated Instincts (23)

Domain	Count
git	3
code-style	6
architecture	3
testing	2
workflow	9

After merging, import with:

/instinct-import .claude/homunculus/instincts/inherited/mcp-rep-instincts.yaml

Files

• .claude/skills/mcp-rep/SKILL.md
• .claude/homunculus/instincts/inherited/mcp-rep-instincts.yaml

---

_{ECC Tools | Everything Claude Code}

[Copilot]

Pull request overview

Adds the missing GitHub “project hygiene” assets (CI workflow + issue/PR templates) referenced by the repo docs, so contributors get consistent automation and reporting structure.

Changes:

• Added a GitHub Actions CI workflow to lint and build the frontend on pushes/PRs to main.
• Added GitHub Issue templates for bug reports and feature requests.
• Added a pull request template (and included a lockfile-only change in frontend/).

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
frontend/package-lock.json	Lockfile updated (removes peer markers in multiple entries).
.github/workflows/ci.yml	New CI job that runs npm ci, npm run lint, and npm run build in frontend/.
.github/pull_request_template.md	New PR template aligned with the CONTRIBUTING guidance.
.github/ISSUE_TEMPLATE/feature_request.md	New feature request issue template.
.github/ISSUE_TEMPLATE/bug_report.md	New bug report issue template.

Files not reviewed (1)

• frontend/package-lock.json: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This PR introduces unrelated churn in the lockfile (removing multiple "peer": true markers) without any corresponding dependency changes. This makes the PR harder to review and can affect reproducibility if different npm versions regenerate the lockfile differently; consider reverting these lockfile-only edits or splitting them into a dedicated dependency/lockfile PR with the npm/node version used to regenerate it.

[Copilot]

CI pins Node.js 20, but the repo’s deployment config uses Node 18 (see netlify.toml) and the README states Node 18+ as the prerequisite. To avoid “works in CI but fails in deploy” drift, align the workflow Node version with the deployment/runtime target (or update the deployment config in a separate change).

Suggested change

	node-version: '20'
	node-version: '18'

[Copilot]

Minor template formatting: the Environment section has - Browser [e.g. ...] missing a colon, unlike the other entries. Adding the colon improves readability and consistency for issue reporters.

Suggested change

	- Browser [e.g. chrome, safari]
	- Version [e.g. 22]
	- Browser: [e.g. chrome, safari]
	- Version: [e.g. 22]