Skip to content

chore: remove 43MB vendored bloat + add STRATEGY/HERMES/security docs#99

Merged
thecelestialmismatch merged 2 commits into
mainfrom
HoundShield/prod-hardening
Jun 3, 2026
Merged

chore: remove 43MB vendored bloat + add STRATEGY/HERMES/security docs#99
thecelestialmismatch merged 2 commits into
mainfrom
HoundShield/prod-hardening

Conversation

@thecelestialmismatch
Copy link
Copy Markdown
Owner

Why

Built on current production main (3b80cc1) — not a stale fork. The light rebrand, doberman logo, mega-menu, $499 pricing hero, and the Supabase auth fix (#97) are already live and are untouched here. This PR only adds what production genuinely still lacks.

What

  • Remove 43MB vendored Claude Code source (compliance-firewall-agent/legacy/brain). Verified not imported by any app code, tsconfig, next.config, package.json, or jest config. Licensing + repo-size liability for a security product. Recoverable from git history.
  • Add STRATEGY.md — brutal-truth verdict (keep product, fix behavior), competitive landscape with sources, the 45-day customer-conversation experiment, 3 money ideas, and the scope refusals (no cold-spam bot, no 12-bot swarm, no 7-day SEO feat: polish branding, enhance ShieldReady dashboard, and update layout/config #1).
  • Add HERMES.md — one lean operating prompt (session ritual, caveman default, small on-demand agent team) replacing the three dead "beast prompt" docs.
  • Add .github/workflows/security.yml — gitleaks secret scan + npm high-severity dependency audit on every push/PR + weekly.

Test plan

  • Vercel preview build passes (only change touching code is the removal of unimported dead code).
  • gitleaks job runs clean on first push.
  • No design/UI change — homepage, pricing, nav, logo identical to production.

🤖 Generated with Claude Code

Built on top of current production main (3b80cc1). The light rebrand, doberman
logo, and the Supabase auth fix (#97) are already live on main and untouched here.

- Remove 43MB vendored Claude Code source (compliance-firewall-agent/legacy/brain).
  Verified not imported by any app code or config; licensing + repo-size liability
  for a security product. Recoverable from git history if ever needed.
- Add STRATEGY.md: brutal-truth verdict, competitive landscape with sources,
  the 45-day customer-conversation experiment, money ideas, and scope refusals.
- Add HERMES.md: one lean operating prompt (session ritual, caveman default,
  small on-demand agent team) replacing the dead "beast prompt" docs.
- Add .github/workflows/security.yml: gitleaks secret scan + npm high-severity
  dependency audit on every push/PR + weekly sweep.
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 3, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
compliance-firewall-agent Ready Ready Preview, Comment Jun 3, 2026 1:39am

@supabase
Copy link
Copy Markdown

supabase Bot commented Jun 3, 2026

This pull request has been ignored for the connected project qifynzuyrdxmxlumpsrq because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

…t-only

- HeroSection snapshot embedded a live "days until Nov 10 2026" countdown from
  new Date(), so it drifted by one every calendar day and CI went red on any day
  except the snapshot's generation date (passed June 2, failed June 3). Freeze
  the clock with vi.setSystemTime in the test and regenerate the snapshot so it
  is deterministic on every CI run. Full suite: 451/451 pass.
- security.yml: mark gitleaks + npm-audit jobs continue-on-error (report-only).
  Soft-launch posture so a new security workflow surfaces findings without
  blocking every merge on pre-existing transitive vulns / historical example
  strings. Tighten to blocking after the dependency tree + history are cleaned.
@thecelestialmismatch thecelestialmismatch merged commit c3c7dfa into main Jun 3, 2026
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant