docs: align setup and supported workflows with current contracts

[SHAURYAKSHARMA24]

Summary

Document the durable DB queue and supported Node floor, add PowerShell backend setup, explain actual language/manual CI coverage, label illustrative architecture, correct branch-refresh underclaim and use GitHub issue support.

Linked issue

Related to #551.

Scope

Audit F19; baseline dev df0e82be3d7b2b7d846eefc1bcf82bde834936f2. This corrects independently verified existing behavior and advances the linked issue without adding product scope.

What changed

Document the durable DB queue and supported Node floor, add PowerShell backend setup, explain actual language/manual CI coverage, label illustrative architecture, correct branch-refresh underclaim and use GitHub issue support.

Acceptance criteria completed

Implementation and targeted regression coverage below. See remaining work for conditions not verified.

Testing performed

Capability registry regeneration and drift check passed (63 mappings); registry tests and Ruff results recorded separately; marketing lint and production build passed.

Current head: b9758c5522e2fa85625f208d707ec2ffc42c9a5c; check snapshot appears below.

Screenshots

Local screenshots and browser measurements are recorded in the remediation delivery report where applicable. Backend-only changes use contract/regression evidence.

Security and data considerations

Preserves owner scoping, source provenance, sealed graph contracts and historical data. No security gate weakened. Rollback: revert this scoped commit; see issue for migration/deployment implications.

Dependencies and blocked work

Independent dev-based PR unless explicitly stated in the issue. No unmerged changes included.

Scope changes or remaining work

Registration #510 and social #512 remain separate. Trust-copy PR #527 edits other FAQ entries; reconcile generated capability docs with OAuth PR #541. Visual review and required current-head CI.

Please review @parthrohit22.

Contributor checklist

• Targets dev; dedicated fork branch from latest dev; issue claimed.

• Scope/evidence recorded; unrelated changes and secrets excluded.

• Targeted validation results reported accurately.

• Required current-head CI and maintainer review complete.

Current-head remediation validation

Head: b9758c5522e2fa85625f208d707ec2ffc42c9a5c.

Capability registry regeneration and drift check passed (63 mappings); registry tests and Ruff results recorded separately; marketing lint and production build passed.

Registration #510 and social #512 remain separate. Trust-copy PR #527 edits other FAQ entries; reconcile generated capability docs with OAuth PR #541. Visual review and required current-head CI.

Checks at delivery: Repository Hygiene: SUCCESS; Analyze (javascript-typescript): SUCCESS; Analyze (python): SUCCESS; API Contract Drift: SUCCESS; Frontend: FAILURE; Backend: SUCCESS; Docker Build: SUCCESS; Marketing Site: SUCCESS; Prototype Browser Acceptance: SKIPPED; Vercel: FAILURE; CodeQL: SUCCESS. Required checks/reviews must pass before merge; deployment authorization was not granted.

[vercel]

@SHAURYAKSHARMA24 is attempting to deploy a commit to the parthrohit60-3117's projects Team on Vercel.

A member of the Team first needs to authorize it.