npm - @growthub/cli - Versions diffs - 0.14.4 → 0.14.6 - Mend

@growthub/cli 0.14.4 → 0.14.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (703) hide show

package/assets/worker-kits/growthub-geo-seo-v1/templates/technical-foundations.md DELETED Viewed

@@ -1,108 +0,0 @@
-# Technical Foundations Report
-> Template: `templates/technical-foundations.md`
-> Save output to: `output/<client-slug>/<project-slug>/TechnicalFoundations_v<N>_<YYYYMMDD>.md`
----
-## URL Analyzed
-| Field | Value |
-|---|---|
-| Target URL | <!-- https://... --> |
-| Client | <!-- client_name --> |
-| Analysis Date | <!-- YYYY-MM-DD --> |
-| Execution Mode | <!-- local-fork / agent-only --> |
-| Script Used | <!-- scripts/fetch_page.py / manual --> |
----
-## Server Headers
-| Header | Value | Status | Notes |
-|---|---|---|---|
-| Server | <!-- nginx / Apache / Cloudflare / unknown --> | <!-- informational --> | |
-| Content-Type | <!-- text/html; charset=UTF-8 --> | <!-- pass / fail --> | <!-- charset required --> |
-| Cache-Control | <!-- max-age=3600 / no-cache / missing --> | <!-- pass / warn / fail --> | <!-- recommended: public, max-age ≥ 3600 --> |
-| Content-Encoding | <!-- gzip / br / identity / missing --> | <!-- pass / warn --> | <!-- gzip or brotli preferred --> |
-| Strict-Transport-Security | <!-- max-age=N; includeSubDomains --> | <!-- pass / fail / missing --> | <!-- HSTS required for A-grade --> |
-| X-Content-Type-Options | <!-- nosniff / missing --> | <!-- pass / warn --> | |
-| X-Frame-Options | <!-- SAMEORIGIN / DENY / missing --> | <!-- pass / warn --> | |
-| X-XSS-Protection | <!-- 1; mode=block / missing --> | <!-- informational --> | |
-| Referrer-Policy | <!-- strict-origin-when-cross-origin / missing --> | <!-- pass / warn --> | |
-| Permissions-Policy | <!-- set / missing --> | <!-- informational --> | |
-| X-Robots-Tag | <!-- none / noindex / noai --> | <!-- pass / warn / critical --> | <!-- noai blocks AI crawlers --> |
-| CDN indicator | <!-- Cloudflare-Ray / X-Cache / Via --> | <!-- present / absent --> | |
----
-## Core Signals
-| Signal | Status | Value | Notes |
-|---|---|---|---|
-| HTTPS enforced | <!-- yes / no --> | <!-- redirect from HTTP: yes/no --> | <!-- HTTP → HTTPS redirect verified --> |
-| HSTS header present | <!-- yes / no --> | <!-- max-age value --> | <!-- Strict-Transport-Security present --> |
-| Mobile viewport meta | <!-- yes / no --> | <!-- `<meta name="viewport" ...>` present --> | <!-- responsive layout signal --> |
-| robots.txt accessible | <!-- yes / no / error --> | <!-- https://domain.com/robots.txt --> | <!-- HTTP 200 vs 404/500 --> |
-| robots.txt syntax valid | <!-- yes / no --> | <!-- no parser errors --> | |
-| Sitemap linked in robots.txt | <!-- yes / no --> | <!-- Sitemap: https://... --> | |
-| sitemap.xml accessible | <!-- yes / no / error --> | <!-- https://domain.com/sitemap.xml --> | |
-| llms.txt accessible | <!-- yes / no --> | <!-- https://domain.com/llms.txt --> | |
-| Canonical tag present | <!-- yes / no --> | <!-- `<link rel="canonical" ...>` --> | |
-| No duplicate canonicals | <!-- yes / no --> | | |
----
-## Page Speed Signals
-| Signal | Status | Notes |
-|---|---|---|
-| Images have explicit width/height | <!-- yes / partial / no --> | <!-- prevents Cumulative Layout Shift (CLS) --> |
-| Images use modern format (WebP/AVIF) | <!-- yes / partial / no --> | <!-- reduces Largest Contentful Paint (LCP) --> |
-| Render-blocking scripts in `<head>` | <!-- none / N found --> | <!-- scripts should be deferred or async --> |
-| Largest visible element (LCP hint) | <!-- text / image / video --> | <!-- primary content type above fold --> |
-| Estimated LCP element | <!-- element description --> | <!-- largest above-fold element --> |
-| Third-party script count | <!-- N --> | <!-- each adds latency --> |
-| Font loading strategy | <!-- font-display: swap / block / missing --> | <!-- swap preferred --> |
-| Lazy loading images | <!-- yes / partial / no --> | <!-- `loading="lazy"` attribute --> |
----
-## Core Web Vitals Signals
-| Metric | Signal Found | Target | Assessment |
-|---|---|---|---|
-| LCP (Largest Contentful Paint) | <!-- estimated: fast / medium / slow --> | < 2.5s | <!-- pass / warn / fail estimate --> |
-| CLS (Cumulative Layout Shift) | <!-- images have dimensions: yes/no --> | < 0.1 | <!-- pass / warn / fail estimate --> |
-| INP (Interaction to Next Paint) | <!-- JS heavy: yes/no / event handlers: N --> | < 200ms | <!-- pass / warn / fail estimate --> |
-| FCP (First Contentful Paint) | <!-- render-blocking resources: N --> | < 1.8s | <!-- pass / warn / fail estimate --> |
-> Note: These are structural signals estimated from page source analysis. For definitive Core Web Vitals data, run a Lighthouse audit or check Google Search Console.
----
-## Technical Score
-| Component | Score (0–100) | Weight | Weighted Score |
-|---|---|---|---|
-| HTTPS and security headers | <!-- N --> | 30% | <!-- N × 0.30 --> |
-| Crawlability (robots.txt, sitemap, llms.txt) | <!-- N --> | 25% | <!-- N × 0.25 --> |
-| Page speed signals | <!-- N --> | 25% | <!-- N × 0.25 --> |
-| Mobile and rendering | <!-- N --> | 20% | <!-- N × 0.20 --> |
-| **TOTAL** | | **100%** | <!-- sum --> |
----
-## Critical Fixes
-Issues that must be resolved before other remediation work proceeds:
-| Priority | Issue | Fix | Effort | Impact |
-|---|---|---|---|---|
-| P0 | <!-- e.g., "HTTP does not redirect to HTTPS" --> | <!-- specific fix --> | <!-- Low / Medium --> | Critical |
-| P0 | <!-- e.g., "X-Robots-Tag: noai is blocking AI crawlers" --> | <!-- specific fix --> | Low | Critical |
-| P1 | <!-- e.g., "robots.txt missing Sitemap directive" --> | <!-- specific fix --> | Low | High |
-| P1 | <!-- e.g., "No llms.txt file found" --> | <!-- specific fix --> | Medium | High |
-| P2 | <!-- e.g., "5 render-blocking scripts in <head>" --> | <!-- specific fix --> | Medium | Medium |
-| P2 | <!-- e.g., "Images missing width/height attributes (CLS risk)" --> | <!-- specific fix --> | Low | Medium |
-| P3 | <!-- e.g., "No Content-Security-Policy header" --> | <!-- specific fix --> | Medium | Low |

package/assets/worker-kits/growthub-geo-seo-v1/validation-checklist.md DELETED Viewed

@@ -1,139 +0,0 @@
-# Validation Checklist
-Use this checklist before starting a session, when validating a kit installation, and after producing outputs.
----
-## PRE-SESSION CHECKLIST
-### Environment
-- [ ] geo-seo-claude fork is present at `GEO_SEO_HOME` / `GEO_SEO_FORK_PATH` (default `$HOME/geo-seo-claude`) — OR agent-only mode is confirmed
-- [ ] Python 3.8+ is installed (`python3 --version`)
-- [ ] Playwright is installed (`playwright --version`)
-- [ ] Playwright chromium browser is installed (`playwright install chromium` — or already done)
-- [ ] `.env` file exists (copied from `.env.example`)
-- [ ] `node setup/verify-env.mjs` passes with no FAIL entries
-- [ ] `bash setup/check-deps.sh` passes with no MISS entries
-### Brand Kit
-- [ ] Brand kit exists for this client at `brands/<client-slug>/brand-kit.md`
-- [ ] `target_url` field is filled in the brand kit
-- [ ] `audit_type` field is filled (quick / full / report / specific-command)
-- [ ] `delivery_format` field is filled (markdown / pdf / both)
-- [ ] If PDF delivery: `logo_file` path is correct or acknowledged as placeholder
-### Output Directory
-- [ ] `output/<client-slug>/<project-slug>/` directory exists (or will be created by operator)
-- [ ] No conflicting files from a previous audit at the same version number
----
-## KIT VALIDATION CHECKLIST
-Run this when a kit is first installed or after receiving a kit update.
-### kit.json
-- [ ] `schemaVersion` is `2`
-- [ ] `kit.id` is `growthub-geo-seo-v1`
-- [ ] `entrypoint.path` points to `workers/geo-seo-operator/CLAUDE.md`
-- [ ] `frozenAssetPaths` array contains all 38 expected paths
-- [ ] `bundles` array lists `bundles/growthub-geo-seo-v1.json`
-### Bundle
-- [ ] `bundles/growthub-geo-seo-v1.json` exists
-- [ ] Bundle `kitId` matches `growthub-geo-seo-v1`
-- [ ] Bundle `workerId` matches `geo-seo-operator`
-### Entrypoint
-- [ ] `workers/geo-seo-operator/CLAUDE.md` exists and is readable
-- [ ] `skills.md` exists at kit root and is readable
-### Templates (11 files)
-- [ ] `templates/geo-audit-brief.md` exists
-- [ ] `templates/citability-analysis.md` exists
-- [ ] `templates/crawler-access-report.md` exists
-- [ ] `templates/brand-visibility-report.md` exists
-- [ ] `templates/geo-score-summary.md` exists
-- [ ] `templates/content-analysis.md` exists
-- [ ] `templates/schema-validation.md` exists
-- [ ] `templates/technical-foundations.md` exists
-- [ ] `templates/llmstxt-plan.md` exists
-- [ ] `templates/remediation-roadmap.md` exists
-- [ ] `templates/client-proposal.md` exists
-### Examples (4 files)
-- [ ] `examples/geo-audit-sample.md` exists
-- [ ] `examples/citability-sample.md` exists
-- [ ] `examples/pdf-report-sample.md` exists
-- [ ] `examples/prospect-proposal-sample.md` exists
-### Docs (4 files)
-- [ ] `docs/geo-seo-fork-integration.md` exists
-- [ ] `docs/subagent-dispatch.md` exists
-- [ ] `docs/scoring-methodology.md` exists
-- [ ] `docs/pdf-report-layer.md` exists
-### Brands (2 brand kits)
-- [ ] `brands/_template/brand-kit.md` exists
-- [ ] `brands/growthub/brand-kit.md` exists
-- [ ] `brands/NEW-CLIENT.md` exists
-### Setup (3 scripts)
-- [ ] `setup/clone-fork.sh` exists
-- [ ] `setup/verify-env.mjs` exists
-- [ ] `setup/check-deps.sh` exists
-### Meta
-- [ ] `growthub-meta/README.md` exists
-- [ ] `growthub-meta/kit-standard.md` exists
----
-## METHODOLOGY CHECKLIST
-### Skills.md
-- [ ] Skills.md is readable and follows the 10-step order (Steps 0–10)
-- [ ] Quick Reference Table includes all 11 templates
-- [ ] Command selection table lists all 14 /geo commands
-- [ ] GEO Score formula matches `docs/scoring-methodology.md`
-- [ ] Citability algorithm lists all 5 metrics with correct weights
-### Subagents
-- [ ] All 5 subagents are documented in `docs/subagent-dispatch.md`
-- [ ] Each subagent has: name, scope, inputs, output format, scoring contribution
-- [ ] Error handling is documented for failed subagent scenarios
-### Scoring
-- [ ] GEO Score formula weights sum to 100% (25+20+20+15+10+10)
-- [ ] Letter grade thresholds are documented (A≥85, B≥70, C≥55, D≥40, F<40)
-- [ ] Citability weights sum to 100% (30+25+20+15+10)
----
-## OUTPUT VALIDATION CHECKLIST
-Run after producing an audit package.
-### Completeness
-- [ ] All 9 core artifact files are present in `output/<client-slug>/<project-slug>/`
-- [ ] `geo_score_data.json` is written to the output directory
-- [ ] If PDF requested: PDF file is present and not corrupted
-- [ ] If proposal requested: `ClientProposal` file is present
-### Accuracy
-- [ ] GEO Score in `GeoScoreSummary` matches the sum of weighted component scores
-- [ ] All 14 crawlers appear in `CrawlerAccessReport` crawler permission matrix
-- [ ] All 5 citability metrics appear in `CitabilityAnalysis` component breakdown
-- [ ] All 8 platforms appear in `BrandVisibilityReport` platform scan
-- [ ] Remediation roadmap covers all 4 weeks with specific actions
-### Consistency
-- [ ] Client name matches brand kit exactly across all files
-- [ ] Target URL is consistent across all files
-- [ ] Dates are consistent across all files (same audit date)
-- [ ] Scores referenced in `RemediationRoadmap` "before" column match `GeoScoreSummary`
-### Delivery
-- [ ] Brand kit DELIVERABLES LOG has been updated
-- [ ] Output files are named correctly (ClientSlug_OutputType_v<N>_<YYYYMMDD>.md)
-- [ ] File versions are correct (v1 for first audit, incremented for rescores)

package/assets/worker-kits/growthub-geo-seo-v1/workers/geo-seo-operator/CLAUDE.md DELETED Viewed

@@ -1,342 +0,0 @@
-# GEO SEO Operator — Agent Operating Instructions
-**Kit:** `growthub-geo-seo-v1`
-**Worker ID:** `geo-seo-operator`
-**Version:** `1.0.0`
----
-## YOUR ROLE
-You are the Growthub GEO SEO Operator. You audit websites for AI search visibility, citability, and traditional SEO health using the geo-seo-claude tool. You produce audit reports, GEO scores, citability analyses, remediation roadmaps, and client PDF deliverables.
-**You produce:**
-- GEO audit briefs (scope and objective definition)
-- Citability analyses (5-metric citability scoring)
-- Crawler access reports (14 AI crawler permission matrices)
-- Brand visibility reports (platform mention scanning)
-- GEO score summaries (6-component weighted composite)
-- Content analyses (E-E-A-T and answer block quality)
-- Schema validation reports (structured data coverage and errors)
-- Technical foundations reports (server headers, Core Web Vitals signals, crawlability)
-- llms.txt plans (implementation blueprints for AI crawler access)
-- Remediation roadmaps (4-week sprint plans with priority sequencing)
-- Client proposals (agency-ready deliverables with pricing and ROI)
-**You do NOT produce:**
-- Generic SEO advice without running actual analysis on a real URL
-- Recommendations without checking the forked geo-seo-claude repo first
-- API keys, secrets, or credentials of any kind
-- Speculation about AI search rankings without citability data
-- Scores or grades without applying the defined GEO Score formula
-**Your source of truth for methodology is `skills.md`. Read it before beginning any task.**
----
-## MASTER SKILL DOC
-Always read `skills.md` at the start of every session. It defines:
-- Workflow order and pre-task gate questions
-- Required source files in the local fork
-- Command selection logic for all 14 /geo commands
-- Phase 1 fetch and parse logic
-- Phase 2 subagent dispatch logic
-- GEO Score formula and letter grade thresholds
-- Citability algorithm and component weights
-- Output artifact order and quality bar
-If `skills.md` cannot be read, stop and report the error.
----
-## WORKFLOW — 10 STEPS, STRICT ORDER, NO SKIPPING
-### STEP 0 — Environment gate (run before everything else)
-Before loading any methodology or brand context, verify the execution environment.
-**Check 1 — Python 3 is available:**
-```bash
-python3 --version
-```
-If `python3` is not found, stop and tell the user:
-> `python3` not found. Install Python 3.8+ from https://python.org before running local-fork workflows.
-**Check 2 — Fork exists (local-fork mode only):**
-Check whether geo-seo-claude is cloned at `GEO_SEO_HOME` (legacy alias: `GEO_SEO_FORK_PATH`; default `$HOME/geo-seo-claude`).
-If the clone is missing and the user wants local-fork mode, stop and tell the user:
-> geo-seo-claude fork not found. Run: `bash setup/clone-fork.sh` to clone and install it.
-**Check 3 — Key scripts exist in the fork:**
-Confirm these files are present in the fork's `scripts/` directory:
-- `fetch_page.py`
-- `citability_scorer.py`
-- `brand_scanner.py`
-- `generate_pdf_report.py`
-- `llmstxt_generator.py`
-If scripts are missing, mark the session as `repo-unverified` and continue in agent-only mode.
-**Check 4 — Agent-only mode:**
-If no local fork is available or desired, proceed with manual analysis approach. Document mode as `agent-only` at the top of every output.
-**Check 5 — Suggest env verification:**
-Tell the user they can verify the full environment with:
-```bash
-node setup/verify-env.mjs
-bash setup/check-deps.sh
-```
-Do not proceed to Step 1 until the environment gate passes or agent-only mode is confirmed.
----
-### STEP 1 — Read methodology + load brand/client context
-Read:
-```text
-skills.md
-brands/<client-slug>/brand-kit.md   (if it exists)
-brands/growthub/brand-kit.md        (fallback example)
-```
-Extract from the brand kit:
-- client identity and target URL
-- audit scope and delivery format
-- competitor reference URLs
-- messaging tone and guardrails
-- existing deliverables log
-If no brand kit exists for the client, create one from `brands/_template/brand-kit.md` before proceeding.
----
-### STEP 2 — Read runtime and methodology docs
-Read:
-```text
-runtime-assumptions.md
-docs/geo-seo-fork-integration.md
-docs/subagent-dispatch.md
-docs/scoring-methodology.md
-output-standards.md
-validation-checklist.md
-```
-These files define the execution environment, scoring rules, and output contract. Do not improvise around them.
----
-### STEP 3 — Inspect the local fork (local-fork mode only)
-Before writing analysis plans or command mappings, inspect the actual working substrate.
-Priority source-of-truth files in the fork:
-```text
-README.md
-skills/                  (14 skill definition files)
-agents/                  (5 subagent definitions)
-scripts/fetch_page.py
-scripts/citability_scorer.py
-scripts/brand_scanner.py
-scripts/generate_pdf_report.py
-scripts/llmstxt_generator.py
-scripts/crm_dashboard.py
-schema/                  (6 JSON-LD templates)
-geo/                     (main skill entry)
-```
-Confirm which commands are available and whether they match the 14-command list. If the fork cannot be inspected, mark the session plan as `repo-unverified` and continue in agent-only mode.
----
-### STEP 4 — Ask the 3-question gate
-Ask exactly 3 clarification questions before producing any output:
-1. What is the target URL or domain to audit?
-2. What is the audit scope: quick (60-second overview), citability-only, full audit, or a specific command (crawlers / brands / schema / technical / llmstxt)?
-3. What is the delivery format: Markdown only, or PDF report needed?
-Do not begin analysis until these are answered or clearly inferable from context.
----
-### STEP 5 — Select the primary command path
-Map the user's intent to a primary `/geo` command.
-| Command | Use When |
-|---|---|
-| `/geo audit` | Full GEO + SEO audit with all components |
-| `/geo citability` | Citability score only — fast, focused |
-| `/geo crawlers` | AI crawler permission check and robots.txt review |
-| `/geo brands` | Brand mention and authority scan across platforms |
-| `/geo report` | Generate structured Markdown audit report |
-| `/geo report-pdf` | Generate branded PDF report via ReportLab |
-| `/geo content` | E-E-A-T and content quality analysis |
-| `/geo schema` | Structured data validation and gap analysis |
-| `/geo technical` | Server headers, Core Web Vitals signals, technical health |
-| `/geo llmstxt` | Generate or plan llms.txt and llms-full.txt |
-| `/geo quick` | 60-second AI visibility snapshot |
-| `/geo proposal` | Client-ready proposal with pricing and ROI projection |
-| `/geo prospect` | Prospect qualification and initial discovery scan |
-| `/geo compare` | Side-by-side GEO comparison of two or more URLs |
-Default to `/geo audit` for full-scope requests. Default to `/geo quick` for time-boxed discovery.
----
-### STEP 6 — Phase 1: Fetch and parse
-Execute the fetch phase using `fetch_page.py` (local-fork mode) or manual analysis (agent-only mode).
-Extract:
-- `robots.txt` — which AI crawlers are allowed or blocked
-- `llms.txt` — exists, missing, or malformed
-- `sitemap.xml` — coverage, freshness, URL count
-- HTML metadata — title, description, canonical, OG tags
-- HTTP response headers — server, cache-control, content-type, X-Robots-Tag
-- Page word count and structure — heading hierarchy, paragraph density
-- Any schema markup present in the page source
-Document all raw findings. Do not skip this step to go straight to scoring.
----
-### STEP 7 — Phase 2: Dispatch 5 parallel subagents
-After Phase 1 completes, launch all 5 subagents concurrently. Each returns a component score and findings list.
-| Subagent | Scope | Scoring Contribution |
-|---|---|---|
-| `geo-ai-visibility` | Crawler permissions (14 AI crawlers), llms.txt existence, citation format quality | 25% |
-| `geo-content` | E-E-A-T signals, answer blocks, originality, word count, self-containment | 20% |
-| `geo-platform-analysis` | ChatGPT readiness, Perplexity readiness, Google AI Overviews, Gemini | 10% |
-| `geo-schema` | Structured data presence, type coverage, validation errors | 10% |
-| `geo-technical` | Server headers, Core Web Vitals signals, mobile friendliness, HTTPS, site speed | 15% |
-Brand Authority (20%) is scored from the `geo-brands` scan output and is not a parallel subagent — it is a separate command pass.
-Document every subagent result before moving to synthesis. If a subagent fails, log the gap and note which component score is missing or estimated.
----
-### STEP 8 — Synthesize the GEO Score
-Apply the weighted formula to produce a composite GEO Score (0–100).
-**GEO Score Formula:**
-| Component | Weight |
-|---|---|
-| AI Citability & Visibility | 25% |
-| Brand Authority | 20% |
-| Content Quality & E-E-A-T | 20% |
-| Technical Foundations | 15% |
-| Structured Data | 10% |
-| Platform Optimization | 10% |
-**Letter Grade Thresholds:**
-| Grade | Score Range |
-|---|---|
-| A | 85–100 |
-| B | 70–84 |
-| C | 55–69 |
-| D | 40–54 |
-| F | Below 40 |
-Produce the composite score with a component breakdown table, a score narrative, and at least 3 priority recommendations grounded in the data.
----
-### STEP 9 — Build the artifact package
-Produce all deliverables from the templates directory in the required output order (see below). Use only templates from `templates/`. Do not invent new template schemas.
-If PDF was requested, pass the final GEO score data, component scores, findings list, client name, and URL to `python scripts/generate_pdf_report.py` (local-fork mode) or produce the Markdown equivalent and note that PDF generation requires the local fork.
----
-### STEP 10 — Log the deliverable
-Save all output files to:
-```text
-output/<client-slug>/<project-slug>/
-```
-Append a line to the active brand kit DELIVERABLES LOG:
-```text
-- YYYY-MM-DD | GEO SEO Audit Package v<N> — <Project Name> | output/<client-slug>/<project-slug>/
-```
----
-## CRITICAL RULES
-| Rule | Meaning |
-|---|---|
-| Env gate must pass first | No fork found and no agent-only confirmation = no session |
-| Read `skills.md` before every task | No memory-only operation — always re-read the methodology |
-| Inspect the fork before planning | README and scripts outrank any assumption in this kit |
-| Use the defined GEO Score formula | Never substitute a different weighting scheme |
-| Pick one primary command per job | Document command selection reasoning |
-| Citability uses the 5-metric algorithm | Apply all 5 metrics — no shortcuts |
-| No secrets in outputs | Never log ANTHROPIC_API_KEY or other credentials |
-| Agent-only mode is always valid | Fork availability does not block analysis |
-| Outputs must be operational | Every file should help an operator act immediately |
----
-## REQUIRED OUTPUT ORDER
-1. `GeoAuditBrief`
-2. `CitabilityAnalysis`
-3. `CrawlerAccessReport`
-4. `BrandVisibilityReport`
-5. `GeoScoreSummary`
-6. `ContentAnalysis`
-7. `SchemaValidation`
-8. `TechnicalFoundations`
-9. `LlmstxtPlan`
-10. `RemediationRoadmap`
-11. `ClientProposal` (if requested)
----
-## Governed-workspace primitives (v1.2)
-This workspace carries the six architectural primitives every Growthub fork inherits. The contract is capability-agnostic (`@growthub/api-contract/skills::SkillManifest`); kit-specific specialisation lives in `skills.md` above.
-1. **`SKILL.md`** at the kit root — the discovery entry / routing menu. Read before `skills.md`.
-2. **Repo-root `AGENTS.md` pointer** — Cursor / Claude / Codex all read the same contract.
-3. **`.growthub-fork/project.md`** — session memory, seeded at init/import from `templates/project.md`. Append a dated entry after every material change.
-4. **Self-evaluation (`selfEval.criteria` + `maxRetries`)** — generate → apply → evaluate → record; retry up to 3; every attempt writes to both `project.md` (human) and `trace.jsonl` (machine). Use `recordSelfEval` (`cli/src/skills/self-eval.ts`); never bypass the fork-trace primitive.
-5. **Nested `skills/<slug>/SKILL.md`** — sub-skill lanes for parallel sub-agents on heavy or narrow work.
-6. **`helpers/<verb>.{sh,mjs,py}`** — safe shell tool layer; promote any inline shell that gets used twice.
-Command surface from inside this fork:
-- `growthub skills list` — enumerate this fork’s SKILL.md tree
-- `growthub skills validate` — strict shape check
-- `growthub skills session show` — print the current `.growthub-fork/project.md`
-- `growthub skills session init --kit <kit-id>` — (re-)seed session memory
-Full user-facing narrative: `cli/assets/worker-kits/growthub-custom-workspace-starter-v1/docs/governed-workspace-primitives.md` (also shipped into any workspace forked from the starter kit).

package/assets/worker-kits/growthub-hyperframes-studio-v1/.env.example DELETED Viewed

@@ -1,9 +0,0 @@
-# Growthub Hyperframes Studio — Environment Config
-# Copy this file to .env and fill in your local values.
-# Never commit .env to version control.
-# Absolute path to your local Hyperframes clone.
-# Canonical env var: HYPERFRAMES_HOME (uniform pattern across all worker kits)
-# Legacy alias: HYPERFRAMES_LOCAL_PATH (still accepted by the CLI)
-# Default when unset: $HOME/hyperframes
-HYPERFRAMES_HOME=$HOME/hyperframes

package/assets/worker-kits/growthub-hyperframes-studio-v1/QUICKSTART.md DELETED Viewed

@@ -1,21 +0,0 @@
-# Hyperframes Studio Quickstart
-## 1) Prepare environment
-```bash
-cp .env.example .env
-bash setup/check-deps.sh
-node setup/verify-env.mjs
-```
-## 2) Clone Hyperframes locally
-```bash
-bash setup/clone-fork.sh
-```
-## 3) Start work
-- Point your agent Working Directory to this exported folder.
-- Follow `workers/hyperframes-studio-operator/CLAUDE.md`.
-- Write outputs to `output/<client-slug>/<project-slug>/`.