feat: add governed continuity, authenticated RLS, and recovery runtime

.github/CODEOWNERS

@@ -0,0 +1,11 @@
+# Founding ownership. Add a second maintainer through a governance pull request
+# before enabling required CODEOWNER reviews in branch protection.
+* @jstar0
+
+/.github/ @jstar0
+/SECURITY.md @jstar0
+/GOVERNANCE.md @jstar0
+/docs/superpowers/specs/2026-07-11-vermory-product-constitution.md @jstar0
+/internal/authn/ @jstar0
+/internal/store/postgres/ @jstar0
+/scripts/release-manifest.sh @jstar0

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,79 @@
+name: Reproducible defect
+description: Report a public, reproducible Vermory defect with synthetic or authorized data.
+title: "[Bug]: "
+labels:
+  - bug
+  - needs-triage
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Do not use this form for credential exposure, cross-tenant leakage with real data, or another vulnerability whose public reproduction creates risk. Follow SECURITY.md instead.
+  - type: textarea
+    id: outcome
+    attributes:
+      label: Observed failure
+      description: What happened, and what user or operational task failed?
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected and forbidden behavior
+      description: State what should happen and what must never happen.
+    validations:
+      required: true
+  - type: dropdown
+    id: boundary
+    attributes:
+      label: Primary boundary
+      options:
+        - Workspace-backed continuity
+        - Conversation-backed continuity
+        - Global Defaults
+        - Bridge or rebind
+        - Formation or governance
+        - Retrieval or context delivery
+        - Deletion or lifecycle
+        - Authentication or tenant isolation
+        - Provider or client integration
+        - Packaging, deployment, or recovery
+        - Documentation or tooling
+    validations:
+      required: true
+  - type: input
+    id: revision
+    attributes:
+      label: Vermory revision or version
+      placeholder: commit SHA, tag, or vermory version output
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Minimal reproduction
+      description: Use synthetic or authorized minimized data. Include exact commands when safe.
+      render: shell
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: OS, architecture, PostgreSQL version, client/provider version, and relevant non-secret configuration.
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Redacted evidence
+      description: Logs, hashes, screenshots, or artifacts with credentials and private content removed.
+  - type: checkboxes
+    id: safety
+    attributes:
+      label: Safety confirmation
+      options:
+        - label: I removed credentials, private transcripts, tenant data, database dumps, and personal absolute paths.
+          required: true
+        - label: This can be discussed publicly without increasing security or privacy risk.
+          required: true

.github/ISSUE_TEMPLATE/capability_proposal.yml

@@ -0,0 +1,71 @@
+name: Capability or architecture proposal
+description: Propose a user-visible capability or a durable architecture decision.
+title: "[Proposal]: "
+labels:
+  - proposal
+  - needs-design
+body:
+  - type: textarea
+    id: real_failure
+    attributes:
+      label: Real failure or workflow
+      description: Which real user, client, or operational workflow requires this change?
+    validations:
+      required: true
+  - type: textarea
+    id: outcome
+    attributes:
+      label: User-visible outcome
+      description: Describe what becomes possible or reliable without prescribing the implementation.
+    validations:
+      required: true
+  - type: textarea
+    id: expected_forbidden
+    attributes:
+      label: Expected and forbidden behavior
+      description: Include isolation, stale-state, deletion, privacy, and ambiguity behavior where relevant.
+    validations:
+      required: true
+  - type: dropdown
+    id: continuity
+    attributes:
+      label: Continuity scope
+      multiple: true
+      options:
+        - Workspace-backed continuity
+        - Conversation-backed continuity
+        - Global Defaults
+        - Cross-continuity bridge
+        - Operational or release boundary
+    validations:
+      required: true
+  - type: textarea
+    id: baseline
+    attributes:
+      label: Simpler baseline
+      description: What simpler implementation or existing behavior must be compared?
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance evidence
+      description: Name deterministic gates, real-client execution, negative controls, and explicit non-claims.
+    validations:
+      required: true
+  - type: textarea
+    id: migration
+    attributes:
+      label: Migration and rollback
+      description: Describe affected schema, data, clients, providers, or deployment profiles and how the change can be reversed.
+  - type: checkboxes
+    id: contract
+    attributes:
+      label: Product boundary
+      options:
+        - label: PostgreSQL remains the native semantic authority.
+          required: true
+        - label: Models may propose but cannot silently govern.
+          required: true
+        - label: The proposal does not rely on similarity alone to merge continuity or promote Global Defaults.
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Private security report
+    url: https://github.com/samekind/Vermory/security/advisories/new
+    about: Report leakage, credential exposure, deletion residue, or another security-sensitive issue privately.
+  - name: Contribution and repository workflow
+    url: https://github.com/samekind/Vermory/blob/main/CONTRIBUTING.md
+    about: Read the contribution, evidence, review, and delivery rules before opening an issue.

.github/ISSUE_TEMPLATE/reality_case.yml

@@ -0,0 +1,66 @@
+name: Reality case or benchmark mapping
+description: Contribute an authorized real trajectory, synthetic hard-gate case, or benchmark mapping.
+title: "[Reality]: "
+labels:
+  - reality-case
+  - needs-validation
+body:
+  - type: dropdown
+    id: evidence_level
+    attributes:
+      label: Proposed evidence level
+      options:
+        - public
+        - withheld_local
+        - external sealed attestation
+        - official_dataset
+        - translated_proxy
+        - inspired_case
+    validations:
+      required: true
+  - type: textarea
+    id: source
+    attributes:
+      label: Source authorization and provenance
+      description: Explain why the source may be used, how it is minimized, and what must remain private.
+    validations:
+      required: true
+  - type: textarea
+    id: trajectory
+    attributes:
+      label: Multi-event trajectory
+      description: Describe anchors, event sequence, corrections, distractors, and the downstream task.
+    validations:
+      required: true
+  - type: textarea
+    id: assertions
+    attributes:
+      label: Expected and forbidden assertions
+      description: Prefer deterministic current-fact, stale-fact, scope, deletion, and artifact checks.
+    validations:
+      required: true
+  - type: textarea
+    id: baselines
+    attributes:
+      label: Relevant baselines
+      description: Identify no-context, full-history, summary, retrieval, external backend, or other comparable conditions.
+    validations:
+      required: true
+  - type: textarea
+    id: privacy
+    attributes:
+      label: Privacy and anonymization
+      description: State removed identifiers, path normalization, transcript minimization, and credential scanning.
+    validations:
+      required: true
+  - type: checkboxes
+    id: integrity
+    attributes:
+      label: Evidence integrity
+      options:
+        - label: I will not label repository-readable data as sealed.
+          required: true
+        - label: Failed baselines and attempts will remain in the evidence.
+          required: true
+        - label: The same generated output will not define the task, expected answer, and sole judgment.
+          required: true

.github/dependabot.yml

@@ -0,0 +1,53 @@
+version: 2
+updates:
+  - package-ecosystem: gomod
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+      time: "03:00"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    groups:
+      go-runtime:
+        patterns:
+          - "*"
+
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+      time: "03:30"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    groups:
+      github-actions:
+        patterns:
+          - "*"
+
+  - package-ecosystem: npm
+    directory: /integrations/openclaw
+    schedule:
+      interval: weekly
+      day: monday
+      time: "04:00"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    groups:
+      openclaw:
+        patterns:
+          - "*"
+
+  - package-ecosystem: pip
+    directory: /integrations/hermes
+    schedule:
+      interval: weekly
+      day: monday
+      time: "04:30"
+      timezone: Asia/Shanghai
+    open-pull-requests-limit: 5
+    groups:
+      hermes:
+        patterns:
+          - "*"

.github/pull_request_template.md

@@ -0,0 +1,62 @@
+## Outcome
+
+<!-- Describe the user-visible or operational result, not only the files changed. -->
+
+## Why This Change
+
+<!-- Link the issue, real failure, reality case, hypothesis, design, ADR, or security advisory. -->
+
+## Scope
+
+- Continuity mode or operational boundary:
+- Authoritative state affected:
+- Client/provider surface affected:
+- Explicitly out of scope:
+
+## Product Contract
+
+- [ ] PostgreSQL remains the only native semantic authority.
+- [ ] Models/providers cannot silently grant authority to their output.
+- [ ] Tenant, continuity, lifecycle, privacy, and deletion gates remain enforced before delivery.
+- [ ] Global Defaults remain thin and explicitly governed.
+- [ ] Cross-continuity movement is explicit rather than similarity-driven.
+- [ ] This change does not revive Gemini CLI as an active client target.
+- [ ] Not applicable; this pull request does not change product behavior.
+
+## Verification
+
+<!-- List exact commands and results. Do not write only "tests pass". -->
+
+```text
+command -> result
+```
+
+## Evidence And Claim Boundary
+
+- Evidence level: `none` / `public` / `withheld_local` / `sealed attestation`
+- Real clients/models actually executed:
+- Retained failures or negative controls:
+- This pull request proves:
+- This pull request does not prove:
+
+## Security And Privacy
+
+- [ ] No credential, OIDC token, private key, private transcript, database dump, full environment, or personal absolute path is included.
+- [ ] Fixtures are synthetic or authorized and minimized.
+- [ ] Deletion, leakage, source-injection, and wrong-binding impact has been considered.
+- [ ] Security-sensitive details are handled privately when public disclosure would create risk.
+
+## Migration And Rollback
+
+<!-- Describe schema/config migration, compatibility, and rollback. Write "not applicable" with a reason when appropriate. -->
+
+## Delivery Checklist
+
+- [ ] The change is focused and unrelated cleanup is excluded.
+- [ ] Frozen expectations were added or revised before capability implementation.
+- [ ] Positive and negative tests cover the affected contract.
+- [ ] `bash scripts/repository-policy.sh` passes.
+- [ ] Affected local tests, full Go tests, race tests, and `go vet` pass as applicable.
+- [ ] OpenClaw and Hermes checks pass when their surfaces are affected.
+- [ ] Documentation, evidence, and failure records match the implementation.
+- [ ] The latest pull-request head passes protected `test` and `sign-snapshot` checks.