[Docs]: comprehensive audit reconciliation and monorepo sync

[Gautam25Raj]

Description

This PR resolves all findings from the comprehensive codebase, documentation, and configuration audit across the entire VeriWorkly monorepo (Groups A through H).

Highlights of Changes:

1. Machine-Readable AI/Agent Layer (Group A):

   • Synchronized OpenAPI spec generation across all 5 web apps via scripts/generate-api-docs.mjs (apps/{docs-platform,site,studio,portfolio,blog-platform}/public/openapi.{json,yaml}).
   • Unified session cookie naming to veriworkly-auth.session_token across all agent cards (.well-known/agent.json).
   • Corrected endpoint paths and synchronized llms.txt / llms-full.txt discovery across apps.

2. Pricing, Limits & Product Catalog (Group B & Group C):

   • Clarified 50/day paid GitHub profile import limit in site FAQ data.
   • Replaced provider-specific AI branding with provider-agnostic frontier model language across site layout, config, and FAQs.
   • Reconciled standalone annual pricing across all pricing.md files: Creator Pro ($7.99/mo eq, $95.88/yr) and AI Credits ($4.99/mo eq, $59.90/yr).
   • Removed dead portfolioProSevenDayProductId branch in productCatalog.ts.
   • Fixed broken asset references, copied veriworkly-special.svg template preview, and cleaned dead /og-generator route.

3. Per-App & Package READMEs (Group D):

   • Synchronized apps/server/README.md (cron job count updated to 5, including changelogSyncJob).
   • Corrected blog-platform port to 3003.
   • Updated Studio README with 7 resume and 5 cover letter template details, /share/{username}/{slug} format, and .env.example guidance.
   • Fixed site README ATS quota path to apps/server/src/services/ats/quota.ts and UI package import to import { cn } from "@veriworkly/ui".
   • Updated portfolio README with template creation lifecycle and mock library workflow.

4. Architecture & Guidelines Sync (Group E & Group F):

   • Documented v3 per-document localStorage scheme (veriworkly:docs:v3:doc:{type}:{id}, veriworkly:docs:v3:index, active pointer, and cache keys) and added useCoverLetterStore in state-management.mdx.
   • Standardized WCAG accessibility target to WCAG 2.2 Level AA across PRODUCT.md, veriworkly.md, and coding-standards.mdx.
   • Fixed repository name references (cd veriworkly), updated README.Local.md dev commands (npm run dev:all), and pinned Node.js requirement to v20.19.0+.

5. Coordinated Template Documentation (Group G):

   • Updated template catalog numbers across docs/index.mdx, resume-templates.mdx, and creating-your-first-resume.mdx to reflect 7 resume templates + 5 cover letter templates (12 total built-in templates).
   • Synchronized all template listings and blog post counts (21 published posts) across studio/public/llms.txt, site/public/llms.txt, docs-platform/public/llms.txt, and veriworkly.md.

6. Environment & Contributor Onboarding (Group H):

   • Added all 24 missing variables to apps/server/.env.example (OAuth credentials, AUTH_COOKIE_DOMAIN, ANALYTICS_HASH_PEPPER, DB_POOL_* timeouts, CHANGELOG_*, etc.) and cleaned unread keys.
   • Deleted dead NEXT_PUBLIC_PORTFOLIO_URL and added NEXT_PUBLIC_APP_URL across studio and portfolio envs.
   • Documented scripts/mock-template-library.mjs fallback for building apps/portfolio without private submodule access in apps/portfolio/README.md, local-setup.mdx, monorepo.mdx, and quick-start.mdx.
   • Documented test:browser in coding-standards.mdx and root README.md.
   • Bumped PRICING_VERIFIED_AT to August 2026 in apps/site/config/compare.ts.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• 📝 Documentation update
• 🧪 Tests (adding or updating tests)

Checklist

• I have read the CONTRIBUTING.md document.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes (636 / 636 passing across workspaces).
• Any dependent changes have been merged and published in downstream modules.