feat: add private support intake foundation

[veryCrunchy]

Summary

• add a responsive Vue 3 and TypeScript support portal for private bug reports, feature requests, and support requests without a GitHub account
• add a product-neutral Go intake service with PostgreSQL persistence, encrypted private fields and diagnostic objects, strict per-product ZIP schemas, retention, deletion capabilities, and idempotent receipt reconciliation
• add a versioned OpenAPI contract, production container, local Compose stack, threat model, operations guide, and CI

This foundation intentionally keeps every request private. Maintainer authentication, moderation, public tracker promotion, GitHub synchronization, and abuse controls remain follow-up work before the broader support workflow is complete.

Advances #1

Validation

• go test ./...
• go vet ./...
• npm --prefix frontend run lint
• npm --prefix frontend test (5 tests)
• npm --prefix frontend run build
• npm --prefix frontend audit --omit=dev --audit-level=high (0 vulnerabilities)
• docker build -t obiente-support:local .
• production-shaped PostgreSQL and container smoke test: health, product registry, create, reconcile, private status, delete, and post-delete 404
• headless Firefox render at 1366 px reviewed locally

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic Password	7d579e5	compose.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}