- Replace dashboard calls to local getCurrentGitHubRepo helpers with getCurrentRepo from @fusion/core
- Update engine scheduler PR-monitor startup paths to use shared core repo resolution
- Remove duplicated remote parsing implementations from dashboard and engine packages
- Mark gap analysis finding 6.3 as resolved after centralizing parsing logic
- Add a root .dockerignore to reduce build context and exclude local runtime state
- Add a multi-stage Dockerfile that builds the workspace, runs as non-root, and includes health checks
- Document Docker build/run usage, env vars, persistence, and quick-start commands in README and docs/docker.md
- Add Docker configuration tests in packages/cli/src/docker.test.ts to validate required image and docs expectations
- Add docs/gap-analysis.md with a full end-to-end audit of the current system
- Capture findings across package completeness, test coverage, naming consistency, and error handling
- Document feature and architectural gap assessments plus verification and quality gate results
- Synthesize outcomes into actionable follow-up tasks and prioritized next steps
- Add docs/test-audit-report.md with an end-to-end audit of core, engine, cli, and dashboard test effectiveness
- Document quantitative metrics, runtime snapshots, mock density, assertion quality, and edge-case coverage ratios
- Identify high-risk coverage gaps and flaky hotspots across runtime, CLI, and dashboard modules
- Capture prioritized recommendations and define follow-up tasks FN-1279 through FN-1283
- Add docs/storage.md with a full audit of dashboard localStorage usage and persistence risks
- Catalog backend global/project setting keys, API endpoints, and project SQLite tables
- Document 9 findings with severity levels and concrete remediation recommendations
- Include a prioritized P0–P2 action plan and verification checklist for follow-up work
- Catalog implemented, partial, missing, and non-applicable Paperclip execution patterns in Fusion
- Analyze 25 capability areas with current state, key gaps, and recommended code-level follow-ups
- Identify impacted packages and relative implementation complexity for each gap
- Propose a phased implementation order and link related FN tasks to guide follow-on work
- Add docs index with structured navigation and links across the new documentation set
- Document onboarding and technical foundations with getting-started and architecture guides
- Add detailed CLI and settings references plus feature guides for dashboard, tasks, workflow steps, missions, multi-project, and agents
- Add a contributing guide and polish cross-references between docs pages for discoverability
- Include dashboard screenshots for key views to provide visual context in the guides
- Rename npm packages from @kb/* to @hai/* and update all workspace references
- Rename CLI binary from kb to hai and config directory from .kb to .hai
- Update dashboard UI branding, titles, and references from kb to hai
- Update all test files, CI workflows, and documentation to reflect new naming
- Run comprehensive grep verification to ensure no stale kb references remain
- Add macOS signing script with codesign, notarization, and stapling support
- Add Windows signing script using signtool with PFX certificate
- Integrate signing steps into release and test-release workflows
- Add signing workflow tests and verification coverage
- Add CODE_SIGNING.md documentation and update README
