PawBytes Proposal Automation Suite Setup

Overview

Installs and configures the PawBytes Proposal Automation Suite into a project in a single guided pass: writes config, checks optional dependencies (AssemblyAI, browser-harness, pandoc), scaffolds the shared seller memory workspace, and optionally runs first-run library ingestion. Module identity (name, code, version) comes from assets/module.yaml.

Writes to:

• {project-root}/.pawbytes/config/config.yaml — shared ecosystem config: core settings at root plus a pa section. User-only keys (user_name, communication_language) are never written here.
• {project-root}/.pawbytes/config/config.user.yaml — gitignore-intended personal settings: user_name, communication_language, and any module variable marked user_setting: true (assemblyai_api_key, default_mode, default_proposal_type, default_language, default_pricing_mode, default_hourly_rate, web_research_enabled).
• {project-root}/.pawbytes/config/module-help.csv — registers module capabilities for the help system.
• {project-root}/.pawbytes/proposal-automation-suites/ — shared seller memory workspace (brand, library, proposals, clients, daily). Follows the PawBytes suite convention (marketing-suites, upwork-suites, proposal-automation-suites); v1 is single-seller with no tenant slug, so memory lives at the suite root rather than under sellers/{slug}/.

Both config scripts use an anti-zombie pattern — existing entries for this module are removed before writing fresh ones, so stale values never persist.

{project-root} is a literal token in config values — never substitute it with an actual path. It signals to the consuming LLM that the value is relative to the project root, not the skill root.

Identity