@web42/w42 0.1.4 → 0.1.9

package/skills/web42-publish-prep/assets/readme-template.md

@@ -1,61 +0,0 @@
-# {Agent Name}
-
-<!-- 
-  This is a starting point, not a form. Rewrite it, restructure it, make it yours.
-  The marketplace renders full Markdown — use it. GIFs, videos, screenshots, emoji, whatever tells your story.
-  
-  Screenshots and demo media are managed in .web42/resources/ and appear automatically on the listing.
-  The README is for the narrative — let the resources handle the visuals.
--->
-
-{A bold opening line. What changes for the user when they have you? Don't describe yourself — describe the outcome.}
-
----
-
-## What I Do
-
-{2–3 sentences, max. What's your superpower? Write this like you're explaining to a friend, not a spec sheet.}
-
-## Try Me
-
-{3–5 concrete scenarios. Not features — experiences. Make the reader feel what it's like to work with you.}
-
-- **"Draft my weekly standup notes from yesterday's git commits and Slack threads."**
-- **"Summarize this 40-page PDF into a one-page brief I can send to my team."**
-- **"Monitor my inbox and ping me only when something actually matters."**
-
-<!-- Replace these with real scenarios that match what you actually do. -->
-
-## Install
-
-```bash
-web42 openclaw install @{author}/{name}
-```
-
-{One sentence on what happens after install. Does the agent need a restart? A quick config? A first conversation?}
-
-## Configuration
-
-{List any API keys, tokens, or setup the user needs to provide. Be specific about where to find each one.}
-
-| Variable | What It Is | Where to Get It |
-|----------|-----------|-----------------|
-| `EXAMPLE_API_KEY` | Access token for Example API | [Example Dashboard > Settings > API](https://example.com/settings) |
-
-<!-- Remove this section entirely if the agent needs no configuration. -->
-
----
-
-<!-- 
-  Optional sections you might add:
-  - "How I Work" (high-level, no secrets — just enough to build trust)
-  - "Limitations" (honesty builds credibility)
-  - "Changelog" (what's new in this version)
-  - "Credits" (shoutouts, inspirations)
-  
-  Or make up your own sections. There are no rules here.
-  
-  Tip: Your screenshots and demo video in .web42/resources/ will appear 
-  on the marketplace listing alongside this README. Focus the README on 
-  the story and let the media speak for the visual side.
--->

package/skills/web42-publish-prep/references/file-hygiene.md

@@ -1,109 +0,0 @@
-# File Hygiene Checklist
-
-Before packing, audit the workspace for files that should not ship to buyers. The CLI's pack command automatically excludes some patterns, but manual review catches everything else.
-
-## Automatically Excluded by the CLI
-
-These patterns are hardcoded in the pack command and will never appear in the `.web42/dist/` artifact:
-
-| Pattern | Reason |
-|---------|--------|
-| `auth-profiles.json` | Platform authentication credentials |
-| `MEMORY.md` | Creator's long-term memory — personal context |
-| `memory/**` | Daily memory logs — personal context |
-| `sessions/**` | Session history — personal context |
-| `.git/**` | Version control internals |
-| `node_modules/**` | Dependencies (not portable) |
-| `.DS_Store` | macOS filesystem metadata |
-| `*.log` | Log files |
-| `openclaw.json` | Platform config (contains agent bindings, channel secrets) |
-| `.openclaw/credentials/**` | Platform credentials |
-| `.web42/**` | Metadata folder (marketplace config, sync state, pack output) |
-| `.web42ignore` | Pack ignore config (meta, not content) |
-| `manifest.json` | Shipped separately as structured data |
-| `USER.md` | Always rewritten with a blank template on install |
-
-## `.web42/` Metadata Files (Not Packed)
-
-The `.web42/` folder contains metadata and assets that are synced separately — they are NOT included in the packed agent files:
-
-| File | Purpose | Editable? |
-|------|---------|-----------|
-| `marketplace.json` | Pricing, license, tags | Yes |
-| `resources.json` | Resource file metadata | Yes |
-| `avatar.*` | Agent profile image | Yes |
-| `resources/` | Screenshots, videos, documents | Yes |
-| `sync.json` | Sync state tracking | No — auto-managed |
-| `dist/` | Pack output | No — auto-generated |
-
-**`sync.json`** should never be edited manually. Doing so will break change detection between local and remote. It is safe to delete if you want to force a full re-sync.
-
-## Files to Flag for Manual Review
-
-These are NOT auto-excluded but often contain content that should not ship:
-
-### Personal Data
-
-- **`HEARTBEAT.md`** — If it contains creator-specific tasks, reminders, or routines. Reset to the scaffold default (empty with comments) unless the tasks are part of the agent's intended behavior.
-- **`SOUL.md`** — If it references the creator by name, contains personal preferences, or has inside jokes. Generalize to describe the agent's intended persona, not the creator's personality.
-- **`IDENTITY.md`** — If it contains the creator's chosen name/emoji/avatar. The buyer's agent should form its own identity. Reset to the scaffold template or write a persona description that fits the agent's purpose.
-- **`TOOLS.md`** — If it contains the creator's SSH hosts, camera names, device nicknames, etc. Reset to the scaffold template with example placeholders.
-
-### Secrets and Credentials
-
-- **`.env` / `.env.local`** — Should never be in the workspace root. If present, flag immediately.
-- **`.web42.config.json`** — Contains config variable values from the creator's install. Must not ship.
-- **Hardcoded API keys in skill files** — The CLI strips known patterns (`sk-...`, `ghp_...`, bearer tokens), but custom keys may slip through. Grep for suspicious patterns: long hex/base64 strings, `token`, `secret`, `password`, `apikey`.
-
-### Development Artifacts
-
-- **`.vscode/` / `.cursor/` / `.idea/`** — IDE configuration. Not relevant to buyers.
-- **`__pycache__/` / `*.pyc`** — Python bytecode.
-- **`Thumbs.db`** — Windows thumbnail cache.
-- **`*.bak` / `*.swp` / `*.tmp`** — Editor backup/swap files.
-- **`test/` / `tests/` / `__tests__/`** — Test files, unless they are part of the agent's functionality.
-- **Build outputs** — `dist/`, `build/`, `out/` directories.
-
-### Large or Binary Files
-
-- The pack command skips files larger than 1 MB.
-- Binary files (images, compiled executables) are skipped automatically (UTF-8 decode failure).
-- If the agent needs images (e.g., for the README cover), host them externally or manage them as resources in `.web42/resources/`.
-
-## Using `.web42ignore`
-
-`web42 init` scaffolds a default `.web42ignore` with sensible patterns (IDE folders, env files, test dirs, drafts). Edit it to match your workspace. Syntax: glob patterns, one per line — lines starting with `#` are comments.
-
-```
-# Exclude test fixtures
-tests/**
-fixtures/**
-
-# Exclude draft documents
-drafts/**
-
-# Exclude local scripts not part of the agent
-scripts/local-*.sh
-```
-
-The `.web42ignore` file itself is automatically excluded from the packed artifact.
-
-## Verification
-
-After auditing, always run:
-
-```
-web42 pack --dry-run
-```
-
-This prints:
-
-1. **User ignore patterns** loaded from `.web42ignore` (shown with ✕ prefix)
-2. **Every file** that would be included, with sizes
-3. **File and config variable counts**
-
-Review the output for:
-
-- **Unexpected files** — anything you don't recognize or didn't intend to ship
-- **File count** — a typical agent has 5–30 files. Hundreds of files suggests missing ignore patterns.
-- **Sensitive content** — spot-check a few files for leaked secrets or personal data

package/skills/web42-publish-prep/references/manifest-fields.md

@@ -1,142 +0,0 @@
-# manifest.json Field Reference
-
-The manifest describes your agent package. Format version is always `"agentpkg/1"`.
-
-## Required Fields
-
-### `name` (string)
-
-The package identifier. Appears in install commands and URLs.
-
-- **Constraints:** 1–100 characters. Lowercase alphanumeric with hyphens only. Must start with a letter or number. Regex: `^[a-z0-9][a-z0-9-]*$`
-- **Good:** `support-bot`, `code-reviewer`, `daily-digest`
-- **Bad:** `My_Agent`, `Support Bot`, `-agent`
-- **Guidance:** Pick something short, memorable, and descriptive of what the agent does. This becomes the slug in `@author/name`.
-
-### `description` (string)
-
-A short pitch for the agent. Shown in search results and the marketplace listing.
-
-- **Constraints:** 1–500 characters.
-- **Good:** "Drafts weekly team reports from your CRM data and posts them to Slack every Monday."
-- **Bad:** "An AI agent." / "This agent uses GPT-4 to process natural language queries against a database."
-- **Guidance:** Lead with the benefit to the user. What problem disappears? Avoid technical jargon about how it works internally.
-
-### `version` (string)
-
-Semantic version of the package.
-
-- **Constraints:** Must match `MAJOR.MINOR.PATCH` (e.g., `1.0.0`).
-- **Guidance:** Start at `1.0.0` for first publish. Bump `PATCH` for fixes, `MINOR` for new capabilities, `MAJOR` for breaking changes to config or behavior.
-
-### `author` (string)
-
-Your Web42 username. Set automatically by `web42 init` from your auth credentials.
-
-- **Constraints:** Non-empty string.
-- **Guidance:** Don't edit manually — it's populated from `web42 auth whoami`.
-
-## Optional Fields
-
-### `platform` (string)
-
-Target agent platform.
-
-- **Values:** Currently only `"openclaw"`.
-- **Guidance:** Set during `web42 init` based on the platform prompt.
-
-### `skills` (array)
-
-List of skills the agent provides. Each entry has `name` (string) and `description` (string).
-
-- **Auto-detected** from `skills/*/SKILL.md` during init and pack.
-- **Guidance:** Don't edit manually. Add skills by creating `skills/<name>/SKILL.md` in your workspace. Internal skills (with `internal: true` in frontmatter) are automatically excluded.
-
-### `plugins` (string array)
-
-Reserved for future use.
-
-- **Default:** `[]`
-- **Guidance:** Leave empty for now.
-
-### `modelPreferences` (object)
-
-Preferred LLM models for this agent.
-
-- **Fields:** `primary` (string, optional), `fallback` (string, optional)
-- **Example:** `{ "primary": "claude-sonnet-4-20250514" }`
-- **Guidance:** Set `primary` to the model the agent is designed and tested for. The `fallback` is used if the primary is unavailable. During install, the CLI will prompt buyers for the corresponding provider API key.
-
-### `tags` (string array)
-
-Searchable labels for marketplace discoverability.
-
-- **Default:** `[]`
-- **Good:** `["support", "crm", "slack", "weekly-reports"]`
-- **Bad:** `["ai", "agent", "good"]` (too generic)
-- **Guidance:** 3–6 tags. Think about what a buyer would search for. Mix category terms ("support", "finance") with capability terms ("slack-integration", "pdf-generation").
-- **Note:** Tags are also specified in `.web42/marketplace.json`. The marketplace.json tags are the canonical source that gets synced to the remote. If tags exist in both files, the marketplace.json values take precedence during sync. See `references/marketplace-config.md`.
-
-### `coverImage` (string)
-
-Path to a cover image file, relative to workspace root.
-
-- **Guidance:** Optional. A good cover image dramatically improves click-through on the marketplace. Use a 1200x630 or 1200x1200 image.
-- **Note:** For the marketplace listing, the primary visual asset is now the agent avatar at `.web42/avatar.*` and resources in `.web42/resources/`. The `coverImage` manifest field is still supported for backward compatibility but resources are the preferred approach. See `references/resources-guide.md`.
-
-### `demoVideoUrl` (string)
-
-URL to a demo video.
-
-- **Constraints:** Must be a valid URL.
-- **Guidance:** A 1–3 minute video showing the agent in action converts far better than text alone. Host on YouTube, Loom, or similar.
-- **Note:** Demo videos can also be managed as resources in `.web42/resources/` with type `"video"`. Resources are uploaded directly to the marketplace. Use `demoVideoUrl` for externally hosted videos (YouTube, Loom) or `.web42/resources/` for self-hosted files. See `references/resources-guide.md`.
-
-### `configVariables` (array)
-
-Secrets and configuration values that buyers provide during install.
-
-- **Each entry:** `{ key, label, description?, required, default? }`
-  - `key` — Environment variable name (e.g., `SLACK_BOT_TOKEN`)
-  - `label` — Human-readable name shown in the install prompt (e.g., "Slack Bot Token")
-  - `description` — Optional help text explaining where to find this value
-  - `required` — Whether install should block without it
-  - `default` — Optional default value
-- **Auto-detected** from skill files during pack (secrets are stripped and replaced with placeholders).
-- **Guidance:** For each config variable, make the `label` and `description` crystal clear. A buyer who has never seen your agent should understand exactly what to provide and where to get it.
-
-## Example Manifest
-
-```json
-{
-  "format": "agentpkg/1",
-  "platform": "openclaw",
-  "name": "weekly-digest",
-  "description": "Summarizes your team's CRM activity and posts a digest to Slack every Monday morning.",
-  "version": "1.0.0",
-  "author": "alice",
-  "skills": [
-    { "name": "crm-reader", "description": "Query CRM data for weekly activity" },
-    { "name": "slack-poster", "description": "Post formatted messages to Slack channels" }
-  ],
-  "plugins": [],
-  "modelPreferences": { "primary": "claude-sonnet-4-20250514" },
-  "tags": ["crm", "slack", "weekly-reports", "productivity"],
-  "coverImage": "assets/cover.png",
-  "demoVideoUrl": "https://www.youtube.com/watch?v=example",
-  "configVariables": [
-    {
-      "key": "CRM_API_KEY",
-      "label": "CRM API Key",
-      "description": "Found in your CRM dashboard under Settings > API",
-      "required": true
-    },
-    {
-      "key": "SLACK_BOT_TOKEN",
-      "label": "Slack Bot Token",
-      "description": "Create a Slack app at api.slack.com and copy the Bot User OAuth Token",
-      "required": true
-    }
-  ]
-}
-```

package/skills/web42-publish-prep/references/marketplace-config.md

@@ -1,99 +0,0 @@
-# Marketplace Configuration Reference
-
-The file `.web42/marketplace.json` controls how your agent appears and is sold on the Web42 marketplace. It is created automatically by `web42 init` with sensible defaults.
-
-## File Location
-
-```
-.web42/marketplace.json
-```
-
-## Fields
-
-### `price_cents` (number)
-
-The price in cents. `0` means free.
-
-- **Default:** `0`
-- **Examples:** `0` (free), `500` ($5.00), `2999` ($29.99), `10000` ($100.00)
-- **Guidance:**
-  - Free agents get more installs but less revenue. Consider free for simple utilities, paid for specialized workflows.
-  - Look at comparable agents on the marketplace for pricing cues.
-  - $5–$15 is a sweet spot for productivity agents. $20–$50 for specialized professional tools.
-  - You can always start free and add pricing later.
-
-### `currency` (string)
-
-ISO 4217 currency code.
-
-- **Default:** `"usd"`
-- **Values:** Currently only `"usd"` is supported.
-
-### `license` (string | null)
-
-The license under which the agent is distributed. `null` means no license specified.
-
-- **Default:** `null`
-- **Supported values:**
-
-| License | Summary | Best For |
-|---------|---------|----------|
-| `"MIT"` | Permissive. Buyers can do almost anything. | Open tools, community agents |
-| `"Apache-2.0"` | Permissive + patent grant. | Enterprise-friendly tools |
-| `"GPL-3.0"` | Copyleft. Derivatives must also be GPL. | Agents you want to stay open |
-| `"BSD-3-Clause"` | Permissive, similar to MIT. | Academic or research agents |
-| `"Proprietary"` | All rights reserved. No redistribution. | Commercial/paid agents |
-| `"Custom"` | Custom terms defined elsewhere. | Unique licensing needs |
-
-- **Guidance:**
-  - For **free agents** intended as community contributions: `MIT` or `Apache-2.0`.
-  - For **paid agents**: `Proprietary` is the standard choice — buyers get usage rights but cannot redistribute.
-  - If unsure, `MIT` for free and `Proprietary` for paid is a safe default.
-
-### `tags` (string array)
-
-Searchable labels for marketplace discoverability. These are the canonical tags shown on the marketplace listing.
-
-- **Default:** `[]`
-- **Constraints:** Each tag should be lowercase, hyphenated for multi-word.
-- **Good:** `["crm", "slack-integration", "weekly-reports", "productivity"]`
-- **Bad:** `["ai", "agent", "good", "cool"]` (too generic)
-- **Guidance:**
-  - Use 3–6 tags.
-  - Mix **category terms** ("finance", "devops", "support") with **capability terms** ("pdf-generation", "slack-integration", "email-monitoring").
-  - Think about what a buyer would search for to find your agent.
-  - Tags also appear in the manifest — the marketplace.json tags are the canonical source that gets synced to the remote.
-
-## Visibility (Dashboard Only)
-
-Agent visibility is **not** controlled through local files. It is managed exclusively through the Web42 dashboard at `web42.ai`.
-
-The visibility lifecycle:
-
-1. **`private`** (default) — Only you can see it. Use this while developing and preparing.
-2. **`unlisted`** — Accessible via direct link but not in search/browse. Good for beta testers or early feedback.
-3. **`public`** — Visible to everyone on the marketplace. Set this when you're ready to launch.
-
-Remind the user to visit the dashboard to toggle visibility when the agent is ready.
-
-## Example File
-
-```json
-{
-  "price_cents": 999,
-  "currency": "usd",
-  "license": "Proprietary",
-  "tags": [
-    "crm",
-    "slack-integration",
-    "weekly-reports",
-    "productivity"
-  ]
-}
-```
-
-## Sync Behavior
-
-When you run `web42 push`, the contents of `.web42/marketplace.json` are included in the sync snapshot and written to the remote database. When you run `web42 pull`, remote marketplace settings (except visibility) are written back to this file.
-
-Changes made on the dashboard (e.g., editing tags or price via the web UI) will be reflected locally on the next `web42 pull`.

package/skills/web42-publish-prep/references/resources-guide.md

@@ -1,136 +0,0 @@
-# Resources Guide
-
-Resources are the visual media and documents that accompany your agent's marketplace listing: screenshots, demo videos, architecture diagrams, PDF guides, etc. They make listings dramatically more compelling.
-
-## File Locations
-
-```
-.web42/resources.json        # Metadata describing each resource
-.web42/resources/             # The actual resource files
-  screenshot-dashboard.png
-  demo-recording.mp4
-  setup-guide.pdf
-```
-
-## `resources.json` Schema
-
-The file is a JSON array of `ResourceMeta` objects:
-
-```json
-[
-  {
-    "file": "screenshot-dashboard.png",
-    "title": "Dashboard Overview",
-    "description": "The main dashboard showing weekly report generation",
-    "type": "image",
-    "sort_order": 0
-  },
-  {
-    "file": "demo-recording.mp4",
-    "title": "3-Minute Demo",
-    "description": "Watch the agent draft a report from CRM data in real time",
-    "type": "video",
-    "sort_order": 1
-  }
-]
-```
-
-### Fields
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `file` | string | Yes | Filename in `.web42/resources/` |
-| `title` | string | Yes | Display title on the marketplace listing |
-| `description` | string | No | Optional caption or context |
-| `type` | `"image"` \| `"video"` \| `"document"` | Yes | Determines how the marketplace renders it |
-| `sort_order` | number | Yes | Display order (0 = first) |
-
-## Resource Types
-
-### Images
-
-Screenshots, diagrams, architecture overviews, result samples.
-
-- **Recommended:** 1200x800 or 1600x900 (16:9 landscape)
-- **Formats:** PNG, JPEG, WebP
-- **Max size:** 5 MB per file
-- **Tips:**
-  - Lead with your best screenshot — it appears first in the gallery.
-  - Show the agent *in action*, not just a static interface.
-  - Annotate screenshots with callouts if key features are not obvious.
-  - Dark-mode and light-mode variants both work well.
-
-### Videos
-
-Demo recordings, walkthroughs, setup tutorials.
-
-- **Recommended:** 1–3 minutes for demos, under 60 seconds for teasers
-- **Formats:** MP4, WebM
-- **Max size:** 50 MB per file (for local storage; consider hosting large videos externally)
-- **Tips:**
-  - Start with the outcome, not the setup. Show the result in the first 10 seconds.
-  - Screen recordings with voiceover convert better than silent ones.
-  - For large video files, consider hosting on YouTube/Loom and linking via `demoVideoUrl` in the manifest instead.
-
-### Documents
-
-PDF guides, setup instructions, architecture docs.
-
-- **Formats:** PDF
-- **Max size:** 10 MB per file
-- **Tips:**
-  - Use for detailed setup guides that are too long for the README.
-  - A 1-page "quick start" PDF is a nice touch for complex agents.
-
-## How Resources Appear on the Marketplace
-
-Resources are displayed on the agent's detail page:
-
-- **Images** show as a scrollable gallery below the agent header.
-- **Videos** embed with a play button.
-- **Documents** appear as downloadable links.
-
-The `sort_order` controls the display sequence across all types.
-
-## Sync Behavior
-
-When you run `web42 push`, the CLI:
-
-1. Reads `.web42/resources.json` for metadata.
-2. Uploads each file from `.web42/resources/` to the server.
-3. Creates the corresponding `agent_resources` rows in the database.
-
-When you run `web42 pull`, the CLI writes `.web42/resources.json` with metadata from the remote. Resource files themselves are not downloaded back (they are referenced by URL in the snapshot).
-
-## Example Workflow
-
-1. Take screenshots of your agent in action.
-2. Save them to `.web42/resources/`.
-3. Create or update `.web42/resources.json` with metadata for each file.
-4. Run `web42 push` — the resources upload alongside everything else.
-
-```json
-[
-  {
-    "file": "slack-report.png",
-    "title": "Weekly Report in Slack",
-    "description": "Automated report posted to #team-updates every Monday",
-    "type": "image",
-    "sort_order": 0
-  },
-  {
-    "file": "crm-dashboard.png",
-    "title": "CRM Data View",
-    "description": "The agent reads from your CRM and extracts key metrics",
-    "type": "image",
-    "sort_order": 1
-  },
-  {
-    "file": "setup-guide.pdf",
-    "title": "Setup Guide",
-    "description": "Step-by-step guide for connecting your CRM and Slack",
-    "type": "document",
-    "sort_order": 2
-  }
-]
-```

package/skills/web42-publish-prep/references/web42-folder.md

@@ -1,120 +0,0 @@
-# The `.web42/` Folder
-
-The `.web42/` directory in your agent workspace is the metadata and sync hub for the Web42 marketplace. It is created automatically by `web42 init`.
-
-## Structure
-
-```
-.web42/
-├── marketplace.json     # Pricing, license, tags
-├── resources.json       # Metadata for resource files
-├── sync.json            # Sync state (auto-managed, do not edit)
-├── avatar.png           # Agent profile image (optional)
-├── resources/           # Screenshots, videos, documents
-│   ├── screenshot-1.png
-│   └── demo.mp4
-└── dist/                # Pack output (auto-generated by web42 pack)
-    ├── AGENTS.md
-    ├── IDENTITY.md
-    ├── manifest.json
-    └── ...
-```
-
-## Files You Edit
-
-### `marketplace.json`
-
-Controls pricing, licensing, and discoverability on the marketplace.
-
-- Created by `web42 init` with defaults.
-- Edit manually or with agent assistance.
-- Synced to/from the remote on push/pull.
-- See `references/marketplace-config.md` for the full field reference.
-
-### `resources.json`
-
-Describes the resource files (screenshots, videos, documents) in the `resources/` subdirectory.
-
-- JSON array of `ResourceMeta` objects.
-- Each entry maps a file in `resources/` to a title, description, type, and display order.
-- See `references/resources-guide.md` for the schema and guidance.
-
-### `avatar.{png,jpg,jpeg,webp,svg}`
-
-The agent's profile image, shown on the marketplace listing and search results.
-
-- Only one avatar file should exist (the CLI picks the first match by extension priority: png, jpg, jpeg, webp, svg).
-- Recommended: 400x400 or larger, square aspect ratio.
-- Uploaded to the server on `web42 push`.
-
-### `resources/`
-
-Directory containing the actual resource files referenced by `resources.json`.
-
-- Drop images, videos, or PDFs here.
-- Filenames must match the `file` field in `resources.json`.
-
-## Files You Should NOT Edit
-
-### `sync.json`
-
-Tracks the sync state between your local workspace and the remote database.
-
-```json
-{
-  "agent_id": "0c4cc49e-...",
-  "last_remote_hash": "7b1d3ecf...",
-  "last_local_hash": "d9a10b8a...",
-  "synced_at": "2026-03-17T03:54:46.124Z"
-}
-```
-
-- **Auto-managed** by `web42 push`, `web42 pull`, and `web42 sync`.
-- Editing this file manually will break change detection.
-- Safe to delete if you want to force a full re-sync (next push/pull will recreate it).
-
-### `dist/`
-
-The pack output directory, generated by `web42 pack` or automatically during `web42 push`.
-
-- Contains the processed, distributable version of your agent files.
-- **Auto-generated** — do not edit files here directly.
-- Excluded from the pack itself (no recursion).
-
-## Git Integration
-
-Add `.web42/sync.json` and `.web42/dist/` to `.gitignore` since they are auto-generated:
-
-```gitignore
-.web42/sync.json
-.web42/dist/
-```
-
-Keep these in version control:
-
-- `.web42/marketplace.json`
-- `.web42/resources.json`
-- `.web42/avatar.*`
-- `.web42/resources/`
-
-## `.web42ignore` (Workspace Root)
-
-Not inside `.web42/` — lives at the workspace root alongside `manifest.json`.
-
-- Created by `web42 init` with sensible defaults (IDE dirs, env files, test folders, drafts).
-- Glob patterns, one per line. Lines starting with `#` are comments.
-- Controls which files are excluded when running `web42 pack` or `web42 push`.
-- Use `web42 pack --dry-run` to verify what gets included/excluded.
-- See `references/file-hygiene.md` for full details.
-
-Keep `.web42ignore` in version control so the ignore rules travel with the project.
-
-## Sync Lifecycle
-
-```
-web42 init     → Creates .web42/, marketplace.json, resources.json, .web42ignore
-web42 pack     → Generates .web42/dist/ from workspace files (respects .web42ignore)
-web42 push     → Sends snapshot (manifest + README + marketplace + files + avatar + resources) to remote
-web42 pull     → Fetches remote snapshot, writes to local files
-web42 sync     → Shows local vs remote hash comparison without changing anything
-```