Skip to content

feat: complete product rebrand to HUNTARA, storage namespace migration, and hierarchical releases - #48

Merged
kjxcodez merged 5 commits into
mainfrom
feat/huntara-rebrand
Sep 19, 2026
Merged

kjxcodez merged 5 commits into
mainfrom
feat/huntara-rebrand

Conversation

@kjxcodez

Copy link
Copy Markdown
Owner

Description

This PR implements the comprehensive product rebrand from LeadForge to HUNTARA, alongside full product identity alignment, storage namespace migration, multi-platform release matrix configuration, and a modernized hierarchical release download architecture.

Executive Overview

  • Product Name: HUNTARA
  • Tagline: "Find the companies worth selling to."
  • Positioning: "HUNTARA helps businesses find and understand their next customers."
  • Scope: End-to-end identity shift across visual assets, desktop application shell, marketing website, documentation, local filesystem storage namespace, monorepo package namespace (@huntara/*), release distribution matrix, and release information architecture.

Key Changes by Domain

1. Visual & Product Brand Identity

  • Asset Deployment: Deployed canonical high-resolution branding assets across desktop application and marketing website:
    • huntara-mark.png & huntara-logo-horizontal.png & huntara-logo-stacked.png
    • icon-192.png, icon-512.png, apple-touch-icon.png, favicon.ico, favicon.png
    • Platform app icons (app-icon.png, app-icon-dark.png, app-icon-light.png, app-icon-monochrome.png, app-icon-alt.png)
  • Desktop Application Shell: Rebranded header, sidebar, workspace switcher, settings screens, notifications, and test modal dialogs.
  • Marketing Site & Documentation: Rebranded navigation, hero sections, feature showcases, case studies, docs, and metadata.

2. Storage & Filesystem Namespace Migration (Zero Data Loss)

  • Canonical Storage Paths:
    • Windows: %APPDATA%\HUNTARA
    • macOS: ~/Library/Application Support/HUNTARA
    • Linux: ~/.config/HUNTARA
  • Automated Migration Engine (apps/desktop/src/main/lib/storage-migration.ts):
    • Automatically detects legacy user data directories (LeadForge, @leadforge/desktop) on startup.
    • Safely copies existing SQLite databases, workspace states, configuration files, and logs into the canonical HUNTARA directory.
    • Preserves legacy data directories intact (non-destructive safety guarantee).
    • Idempotent execution guarded by .huntara-migrated.json migration marker.
    • Validated via standalone simulation test (scripts/test-storage-migration.ts passed 100%).

3. Monorepo Package Namespace Migration (@huntara/*)

  • Renamed All Workspace Packages:
    • @leadforge/agent-core ➔ @huntara/agent-core
    • @leadforge/agent-runtime ➔ @huntara/agent-runtime
    • @leadforge/ai ➔ @huntara/ai
    • @leadforge/auth ➔ @huntara/auth
    • @leadforge/core ➔ @huntara/core
    • @leadforge/logger ➔ @huntara/logger
    • @leadforge/schema ➔ @huntara/schema
    • @leadforge/sdk ➔ @huntara/sdk
    • @leadforge/workflow-engine ➔ @huntara/workflow-engine
    • @leadforge/desktop ➔ @huntara/desktop
    • Root package name updated to huntara.
  • Inter-package Dependencies: Updated all internal workspace:* dependencies and cross-package imports.
  • Backwards Compatibility: Added fallback path aliases in vitest.config.ts to guarantee zero disruptions for legacy references during test execution.

4. Multi-Platform Release Infrastructure

  • Release Matrix Workflow (.github/workflows/release.yml):
    • Windows: windows-latest ➔ .exe NSIS installer + portable executable.
    • macOS: macos-latest ➔ .dmg + .zip (Universal, arm64, x64).
    • Linux: ubuntu-latest ➔ .AppImage.
  • Standardized Artifact Naming:
    • HUNTARA-${version}-${os}-${arch}.${ext}
  • Release Checksums & Update Manifests:
    • Automated generation of SHA-256 checksums and Electron auto-updater manifests (latest.yml, latest-mac.yml, latest-linux.yml).

5. Hierarchical Release Information Architecture & Download Experience

  • Replaced Flat Model with 3-Tier Hierarchy:
    • /releases: Clean release index displaying only released platforms for each version (zero placeholder "coming soon" dead-ends).
    • /releases/[version]: Dedicated version details page highlighting release notes, git commit hashes, and downloadable platforms.
    • /releases/[version]/[platform]: Deep-dive platform landing pages containing:
      • Primary installer and portable binary download links.
      • Verified SHA-256 binary checksums with one-click copyable terminal verification commands (Get-FileHash on Windows, shasum -a 256 on macOS, sha256sum on Linux).
      • Minimum and recommended system requirements table.
      • Step-by-step platform installation and setup instructions.
      • Strict notFound() 404 handling for invalid or unreleased platform combinations (e.g. /releases/v1.2.0-beta/linux returns HTTP 404).
  • Download Hub (/download & <Downloads />):
    • Prominently recommends the latest stable release.
    • Dynamically renders download cards only for platforms with real, verifiable artifacts.
  • Dynamic Sitemap (apps/marketing/app/sitemap.ts):
    • Programmatically indexes all valid release and platform route combinations for search engines.
  • Automated Routing Test Suite (apps/marketing/lib/releases.test.ts):
    • 8 automated tests verifying platform availability resolution, artifact mapping, and 404 routing logic.

Related Issues

  • Closes # (HUNTARA Rebrand, Identity & Multi-Platform Release Initiative)

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactor (code organization, no user-facing visual modifications)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Verification Checklist

Automated Validation

  • pnpm run check-types / pnpm -F marketing typecheck: passes successfully with 0 errors.
  • pnpm run lint / pnpm -F marketing lint: 0 lint errors.
  • pnpm run format: Prettier checks pass cleanly.
  • pnpm test: 80 test files passed (810/810 unit and integration tests passing).
  • pnpm -F marketing test: Platform release architecture routing suite passed (8/8 tests).
  • pnpm -F marketing build: Next.js static site generation succeeded (58/58 pages prerendered, including all dynamic /releases/[version] and /releases/[version]/[platform] routes).
  • pnpm release:check: 10/10 release gates passed (🟢 READY FOR RELEASE).
  • pnpm verify:production: All production integrity checks passed with 0 errors.

Visual Verification (for UI/UX edits)

  • Design adheres strictly to the HUNTARA design system (warm glow accents, dark mode palette, crisp typographic scale).
  • Staggered entrance and transitions execute smoothly across all release and documentation pages.
  • Platform release pages render terminal copy snippets with real-time feedback toast notifications.
  • Modal dialogs and slide-out sheets contain defensive conditional rendering guards to prevent closed-state null exceptions.

Zero-Data-Loss & Backwards Compatibility Guarantee

  • Existing User Data: Existing users upgrading from LeadForge OS will have their workspace databases, local configurations, and logs copied over to %APPDATA%\HUNTARA seamlessly on initial boot.
  • Non-Destructive: Original legacy directories are never modified or purged, ensuring users can safely revert or access historical backup files at any time.
  • Idempotent: Future boots check .huntara-migrated.json and bypass redundant copy operations.

- Deployed exact source brand assets across desktop resources, renderer assets, marketing public, and documentation
- Updated Electron builder packaging: appId 'com.huntara.app', productName 'HUNTARA', icon/shortcut configurations
- Updated Desktop main process: window titles, AppUserModelId, system tray, splash window, updater, and worker plugins
- Updated Desktop renderer: brand tokens (#FA7125 / #E05E18), navigation, brand panel, auth, onboarding, and UI components
- Updated Marketing app: metadata, layouts, navigation, footer, hero, downloads, brand guidelines page, and all static content
- Updated API: authentication emails and auth HTML templates to HUNTARA identity and palette
- Preserved internal package scopes (@leadforge/*), SQLite database naming (leadforge_*.db), and all business logic
- Verified: all 801 tests pass, typechecks pass across all apps, and desktop build passes
@vercel

vercel Bot commented Sep 19, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
leadforge-os-api Ready Ready Preview Sep 19, 2026 10:22pm UTC
leadforge-os-marketing Ready Ready Preview Sep 19, 2026 10:22pm UTC

@kjxcodez
kjxcodez merged commit 0df8abf into main Sep 19, 2026
6 of 10 checks passed

This branch was successfully deployed

2 active deployments
Preview – leadforge-os-marketing — edaaadb7 Deployed Sep 19, 2026 by vercel[bot]
Preview – leadforge-os-api — edaaadb7 Deployed Sep 19, 2026 by vercel[bot]
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