docs: align SUPPORT.md with repo deprecation

[Copilot]

Pull Request

Description

SUPPORT.md still pointed to stale blackroad-dev/prism-console discussion/issue links with no deprecation notice, while README.md already declared the repo deprecated and moved to BlackRoad-OS. Users had no signal in the support doc about where to actually go.

Changes:

• Added ⚠️ deprecated banner at top of SUPPORT.md
• Replaced stale blackroad-dev links with the canonical BlackRoad-OS repo table (mirrors README.md)
• Preserved #help hub, email support, and SECURITY.md references

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Infrastructure/DevOps change

Testing

• Tested locally
• Health checks pass
• Railway deployment succeeds

Checklist

• Code follows project style
• Self-reviewed code
• Updated documentation
• Tests pass

---

🤖 Generated with Claude Code

Original prompt

Do I go back to always asking questions here? Is this repo most capable?

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

Quick Pulse

Field	Value
Author	@Copilot
Branch	copilot/questioning-in-repo-capabilities
Draft?	Yes

Automation wave checklist

• $ python3 scripts/dry-run-csv.py prs-200.csv
• $ bash scripts/make-branches.sh prs-200.csv
• $ bash scripts/bulk-create-prs.sh prs-200.csv

Tip: set DRY_RUN_LIMIT or pass --limit to preview additional CSV entries.

[github-actions]

🔏 Commit Signature Verification Failed

❌ This PR contains unsigned commits and cannot be merged.

Summary:

• Total commits: 1
• ✅ Signed: 0
• ❌ Unsigned: 1

Unsigned commits:
$'\n'- 61c37557a by copilot-swe-agent[bot]: Initial plan

---

📚 How to sign your commits:

Setup GPG signing (one-time):

# Generate GPG key
gpg --full-generate-key

# List keys and copy the key ID
gpg --list-secret-keys --keyid-format=long

# Configure Git to use your key
git config --global user.signingkey YOUR_KEY_ID
git config --global commit.gpgsign true

# Add GPG key to GitHub
gpg --armor --export YOUR_KEY_ID
# Paste output to: GitHub → Settings → SSH and GPG keys

For these commits:

# Option 1: Amend the last commit with signature
git commit --amend --no-edit -S

# Option 2: Rebase and sign all commits
git rebase --exec 'git commit --amend --no-edit -n -S' -i 64e02b5c20ed351a525fe8483b183f4ac2d5d6a4

# Force push (carefully!)
git push --force-with-lease

Alternative: SSH signing (GitHub supports this!)

# Use your existing SSH key
git config --global gpg.format ssh
git config --global user.signingkey ~/.ssh/id_ed25519.pub
git config --global commit.gpgsign true

---

🔐 Security Policy: All commits must be cryptographically signed to ensure authenticity and integrity.

[github-actions]

📝 Status Check Summary

✅ Required Checks (must pass for merge)

• Backend health checks
• Backend integration tests
• Security scanning

⚡ Optional Checks (informational only)

• Vercel preview deployment
• Frontend lint
• Documentation preview

Note: Vercel and frontend previews do not block merges. We prioritize backend functionality and security.