Growth infrastructure: README rewrite, YAML issue forms, SEO, launch content

Task 1: Complete README rewrite — SEO-optimized for "Claude Code memory",
"MCP server memory", "persistent context". Architecture diagram, real MCP
tool call example, features table, 6-item FAQ, CLI reference.

Task 2: GitHub metadata doc — repo description, 20 topics, social preview.

Task 3: YAML issue forms (bug_report.yml, feature_request.yml) replacing
markdown templates. Upgraded PR template, CONTRIBUTING.md with full
monorepo guide, SECURITY.md with SLA and scope.

Task 4: llms.txt for AI search engines, JSON-LD structured data, meta tags.

Task 5: Launch content — HN Show post + first comment, Reddit r/ClaudeAI
and r/LocalLLaMA posts, Product Hunt copy, X thread, LinkedIn post.

Task 6: CHANGELOG.md following Keep a Changelog format.

Task 7: Star farming — cortex doctor prompt, README banner, post-install
message, newsletter CTA.

CI upgraded with ubuntu + macos matrix, npm audit on PRs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: KD-K2N2

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,98 @@
+name: Bug Report
+description: Report a bug or unexpected behavior in Cortex
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report this. Please fill out the fields below so we can reproduce and fix the issue.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear description of what the bug is.
+      placeholder: What happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to Reproduce
+      description: The exact steps to trigger the bug.
+      placeholder: |
+        1. Run `cortex init` in a project
+        2. Start a Claude Code session
+        3. ...
+      value: |
+        1.
+        2.
+        3.
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened instead?
+    validations:
+      required: true
+
+  - type: input
+    id: cortex-version
+    attributes:
+      label: Cortex Version
+      description: Run `cortex --version` and paste the output.
+      placeholder: "1.0.0"
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: Operating System
+      description: e.g. macOS 15.3, Ubuntu 24.04, Windows 11
+      placeholder: "macOS 15.3"
+    validations:
+      required: true
+
+  - type: input
+    id: claude-code-version
+    attributes:
+      label: Claude Code Version
+      description: Run `claude --version` and paste the output.
+      placeholder: "1.0.0"
+    validations:
+      required: false
+
+  - type: dropdown
+    id: install-method
+    attributes:
+      label: Installation Method
+      options:
+        - Homebrew (brew install cortex-memory)
+        - npx (@cortex.memory/cli init)
+        - curl (install script)
+        - Built from source
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant Logs
+      description: Paste output from `cortex logs` or `cortex doctor`. This will be rendered as code.
+      render: shell
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,42 @@
+name: Feature Request
+description: Suggest a new feature or improvement for Cortex
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Feature requests help us prioritize. Please describe what you need and why.
+
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use Case
+      description: What are you trying to do? Describe the problem, not the solution.
+      placeholder: "When I'm working on multiple projects, I need to..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed-solution
+    attributes:
+      label: Proposed Solution
+      description: How do you think this should work? Be specific.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: What else have you tried or thought about?
+    validations:
+      required: false
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Screenshots, links, related issues, or anything else that helps.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,37 +1,28 @@
-## Summary
+## What does this PR do?
 
-Brief description of the changes and the motivation behind them.
+<!-- One or two sentences. Link to the issue if there is one. -->
 
-Fixes # (issue number)
+## Why?
 
-## Type of Change
+<!-- What problem does this solve? Why is this approach the right one? -->
 
-- [ ] Bug fix (non-breaking change that fixes an issue)
-- [ ] New feature (non-breaking change that adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to change)
-- [ ] Documentation update
-- [ ] Performance improvement
-- [ ] Refactoring (no functional changes)
+## How to test it
 
-## How Has This Been Tested?
+<!-- Steps a reviewer can follow to verify this works. -->
 
-Describe the tests you ran to verify your changes.
+1.
+2.
+3.
 
-- [ ] Unit tests pass (`pnpm test`)
-- [ ] Lint passes (`pnpm lint`)
-- [ ] Type check passes (`pnpm typecheck`)
-- [ ] Manual testing with Claude Code
-
-## Checklist
+## Screenshots / recordings
 
-- [ ] My code follows the project's style guidelines
-- [ ] I have performed a self-review of my code
-- [ ] I have added tests that prove my fix is effective or my feature works
-- [ ] New and existing unit tests pass locally with my changes
-- [ ] I have updated documentation where needed
-- [ ] My changes generate no new warnings
-- [ ] Any dependent changes have been merged and published
+<!-- If this changes UI (dashboard, CLI output, VS Code extension), include a screenshot or recording. Delete this section if not applicable. -->
 
-## Screenshots (if applicable)
+## Checklist
 
-Add screenshots for UI changes in the dashboard or VS Code extension.
+- [ ] Tests pass (`pnpm test`)
+- [ ] Types pass (`pnpm typecheck`)
+- [ ] Lint passes (`pnpm lint`)
+- [ ] CHANGELOG.md updated (if user-facing change)
+- [ ] Docs updated (if behavior changed)
+- [ ] Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/)

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -23,8 +23,11 @@ jobs:
       - run: pnpm turbo typecheck
 
   test:
-    runs-on: ubuntu-latest
     needs: lint-and-typecheck
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+    runs-on: ${{ matrix.os }}
     steps:
       - uses: actions/checkout@v4
       - uses: pnpm/action-setup@v3
@@ -37,14 +40,15 @@ jobs:
       - run: pnpm install --frozen-lockfile
       - run: pnpm turbo test
       - name: Upload coverage
+        if: matrix.os == 'ubuntu-latest'
         uses: actions/upload-artifact@v4
         with:
           name: coverage
           path: packages/*/coverage/
 
   build:
-    runs-on: ubuntu-latest
     needs: test
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
       - uses: pnpm/action-setup@v3
@@ -56,3 +60,19 @@ jobs:
           cache: pnpm
       - run: pnpm install --frozen-lockfile
       - run: pnpm turbo build
+
+  audit:
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v3
+        with:
+          version: 10
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: pnpm
+      - run: pnpm install --frozen-lockfile
+      - name: Security audit
+        run: pnpm audit --audit-level=high

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,38 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Planned
+- Multi-machine sync via Turso (libsql) with conflict resolution
+- VS Code extension with memory sidebar and inline context
+- Team sharing — shared memory spaces for engineering teams
+- Memory analytics — usage patterns, most-referenced memories, decay tracking
+- Webhooks — trigger actions when memories are created or updated
+
+## [1.0.0] - 2025-03-22
+
+### Added
+- MCP server with 5 tools: `cortex_get_context`, `cortex_save_memory`, `cortex_search`, `cortex_list_projects`, `cortex_get_status`
+- Session summarizer — AI reviews completed sessions and captures missed context automatically
+- Quality gate with 7 validation rules: content length (50-2000 chars), reason field required (min 10 chars), duplicate detection (TF-IDF similarity < 85%), banned phrase filter, sensitive data blocker (API keys, passwords, tokens, private keys), quality score threshold (3+), rate limiting (50 saves per session, 200 per day)
+- 6 memory types with distinct lifecycles: Decision (permanent), Context (may expire), Preference (permanent), Thread (expires when resolved), Error (persists until fixed), Learning (permanent)
+- Project detection using 4-layer strategy: git remote URL, package.json name, directory name, manual assignment
+- Local SQLite database at `~/.cortex/cortex.db` with full-text search via FTS5
+- 33 CLI commands: init, status, doctor, show, search, add, edit, delete, clear, export, import, backup, start, stop, restart, logs, sync status, sync push, sync pull, config show, config set, config reset, uninstall, version, help, count, history, stats, tag, untag, pin, unpin, archive
+- Web dashboard (Next.js 14) on localhost:7433 with memory browsing, search, bulk operations, project switching, and sync status
+- `cortex doctor` diagnostic command — checks daemon health, database integrity, MCP registration, and configuration
+- Clean uninstall via `cortex uninstall` — removes database, daemon, config, and MCP registration with optional memory export
+- AES-256-GCM encryption for stored credentials (Turso tokens, sync keys)
+- Homebrew tap for macOS installation (`brew install cortex-memory`)
+- npx one-command setup (`npx @cortex.memory/cli init`)
+- curl install script for automated environments
+- Electron desktop app with system tray integration
+- SwiftUI native macOS app (macOS 13+)
+- Zero telemetry by default — no analytics, no crash reporting, no phone-home
+
+This project adheres to [Semantic Versioning](https://semver.org/) and [Keep a Changelog](https://keepachangelog.com/).