chore(governance): fill the template tokens that have a factual answer (#56)

The template tokens in these files had a factual answer, so they are
filled:

- `.github/settings.yml`
- `.github/CODE_OF_CONDUCT.md`

**Left deliberately for the owner** — these ask for values a machine
must not invent (a wrong security contact is worse than an
obviously-unfilled one):

- `.github/CODE_OF_CONDUCT.md`: `{{CONDUCT_EMAIL}}`, `{{CONDUCT_TEAM}}`,
`{{RESPONSE_TIME}}`

Filling those is a one-off decision about estate contact details, not a
per-repo edit.

Author: hyperpolymath

.github/CODE_OF_CONDUCT.md

@@ -310,7 +310,7 @@ We thank these communities for their leadership in creating welcoming spaces.
 
 If you have questions about this Code of Conduct:
 
-- Open a [Discussion](https://{{FORGE}}/hyperpolymath/patch-bridge/discussions) (for general questions)
+- Open a [Discussion](https://github.com/hyperpolymath/patch-bridge/discussions) (for general questions)
 - Email {{CONDUCT_EMAIL}} (for private questions)
 - Contact any maintainer directly
 

.github/settings.yml

@@ -7,13 +7,13 @@
 # applied by the probot/settings app when changes are pushed to the default
 # branch. Install the app at: https://github.com/apps/settings
 #
-# Template file — replace patch-bridge and {{DESCRIPTION}} with actual values.
+# Template file — replace patch-bridge and CVE mitigation lifecycle — from disclosure to verified remediation with reachability analysis and formal soundness with actual values.
 
 # ─── Repository Settings ───────────────────────────────────────────────────────
 
 repository:
   name: "patch-bridge"
-  description: "{{DESCRIPTION}}"
+  description: "CVE mitigation lifecycle — from disclosure to verified remediation with reachability analysis and formal soundness"
   homepage: "https://github.com/hyperpolymath/patch-bridge"
   private: false
   has_issues: true