Add standardized PR and issue templates

[devin-ai-integration]

This PR adds .github/PULL_REQUEST_TEMPLATE.md and .github/ISSUE_TEMPLATE/ forms to align every PR with the issue-driven workflow required by require-issue.yml.

Closes #35.

Link to Devin session: https://app.devin.ai/sessions/869a2071e0e5435386fb51acecdaf72c
Requested by: @bogdanbaciu21

[devin-ai-integration]

Original prompt from Bogdan

Goal: give every one of Dan's own repos a consistent, professional GitHub PR template and issue-template set (mirroring the Devin PR-templates convention at https://docs.devin.ai/integrations/pr-templates), then email Dan a summary. Repos in scope (his own, repo-root .github/ only): bogdanbaciu21/dans-brain, bogdanbaciu21/LJB, bogdanbaciu21/project-lantern, bogdanbaciu21/opg, bogdanbaciu21/project-purpose, bogdanbaciu21/bogdanbaciu-dot-com, bogdanbaciu21/ljb-dashboard-func, bogdanbaciu21/luckygo-product-vision, bogdanbaciu21/ljb-cobalt, bogdanbaciu21/trading-bot, bogdanbaciu21/Corp-Dev-Mission-Control, bogdanbaciu21/skills, bogdanbaciu21/Bogdan-Baciu-Design-System.

REFERENCE TEMPLATE: bogdanbaciu21/opg already has the gold-standard setup — copy its .github/PULL_REQUEST_TEMPLATE.md and .github/ISSUE_TEMPLATE/ (bug.yml, feature.yml, documentation.yml, security-redirect.yml, self-hosting.yml, config.yml) as the base. Do NOT modify opg (it already conforms; only verify).

DO NOT TOUCH: vendored/third-party .github dirs inside repos, e.g. LJB/hill-climb-github/.../courses/*/.github/, LJB/infra/ljb-platform/scaffold/.github/. Only the repo-root .github/ of each repo.

Steps:

1. For each in-scope repo, add .github/PULL_REQUEST_TEMPLATE.md adapted from opg's. CRITICAL: the template MUST keep an issue-reference line at the very top (e.g. "Tracking issue: Fixes #___ or work-ticket id"), because every repo runs require-issue.yml which blocks PRs lacking a ``#123/`GH-123`/closing-keyword/work-ticket reference. Trim opg's self-hosting/community-specific sections for repos where they don't apply (e.g. private/personal repos), but keep Issue/outcome, User impact, Evidence (tests run), Privacy/security, Rollback, Docs, and the Author/Reviewer checklists.
2. For each repo, add .github/ISSUE_TEMPLATE/ with at minimum bug.yml, feature.yml, and config.yml, adapted from opg's, fixing the repo-specific URLs in config.yml (security ... (1758 chars truncated...)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[codeant-ai]

Skipping PR review because a bot author is detected.

If you want to trigger CodeAnt AI, comment @codeant-ai review to trigger a manual review.

[mergify]

Merge Protections

🟢 Merge protection satisfied — ready to merge.

Show 1 satisfied protection

🟢 ready label

• label=ready-to-merge

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[devin-ai-integration]

@Mergifyio queue

[mergify]

queue

⚠️ Configuration not compatible with a branch protection setting

Details

The branch protection setting Require branches to be up to date before merging is not compatible with draft PR checks. To keep this branch protection enabled, update your Mergify configuration to enable in-place checks: set merge_queue.max_parallel_checks: 1, set every queue rule batch_size: 1, and avoid two-step CI (make merge_conditions identical to queue_conditions). Otherwise, disable this branch protection.