- JavaScript 100%
Add a self-contained S2W2 plugin verification path so third parties can test Sweetheart without the private parent repo, live platform, miniprogram, or secrets. Includes a local mock platform, miniprogram/user actor simulator, counterparty agent simulator, happy-path scenario, verification assertions, npm scripts, and gitignore rules for generated harness output. Verification: - npm run verify: PASS - Structure check: PASS - Local Sweetheart harness: 20/20 passed - Harness report sha256: 1b04a3c20e260a562d28812f2b37ff5cc7435f0c0735045389d982fdb4bbb447 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| sweetheart | ||
| test/plugin-harness | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| package.json | ||
| README.md | ||
| submissions.json | ||
| SUBMISSIONS.md | ||
ClawLove S2W2 — Sweetheart Prototype Delivery
This repository is the minimal S2W2 delivery package for proving the ClawLove Sweetheart agent concept with a third-party reviewer.
The package intentionally focuses on the executable Sweetheart plugin surface: agent instructions, skills, tool descriptors, initial memory, and a lightweight eval guide. It does not include production credentials, internal design notes, generated outputs, or platform deployment assets.
Included scope
sweetheart/
├── AGENT.md # Agent entry point and state machine
├── INSTALL.md # Third-party install and smoke-test guide
├── README.md # Bundle structure and operating notes
├── manifest.json # Plugin metadata and trigger hints
├── .claude-plugin/plugin.json # Claude plugin descriptor
├── memory/ # Initial state and schema
├── skills/ # Nurture, roam, dialogue, social, report skills
├── tools/ # Platform/API and local contact DB tool descriptors
└── eval/ # Optional live-platform dual-agent helpers
test/plugin-harness/
├── run_harness.js # Local mock-platform + user simulator runner
├── mock_platform.js # Rule-driven platform op simulator
├── user_actor.js # Miniprogram/user action simulator
├── opponent_claw_actor.js # Counterparty agent simulator
├── verify_results.js # Assertions and report export
└── scenarios/happy_path.json # Happy-path script
Repository metadata files (CONTRIBUTING.md, SUBMISSIONS.md, submissions.json) are retained for the external delivery workflow.
Prerequisites
- Node.js 20+ and npm for local syntax/eval helper checks.
- No live platform is required for
npm run verify; S2W2 includes a mock platform and miniprogram/user simulator. - A compatible agent runtime is required only for manual/live-agent review of
sweetheart/AGENT.md,sweetheart/skills/,sweetheart/tools/, andsweetheart/memory/. - Platform URL and tokens are required only for optional live-platform eval helpers. Secrets are supplied by the tester/deployer and never committed.
Basic verification
From this repository root:
npm run verify
Expected result:
verify:structureprintsstructure ok.test:pluginstarts the local Sweetheart harness.- The harness validates bundle structure, JSON-readable tool descriptors, AGENT.md line count, mock platform calls, miniprogram/user responses, counterparty agent dialogue, and final report assertions.
- The happy-path report ends with
20/20passed.
The local harness does not require the private parent repository, real platform, real miniprogram, or secrets. It simulates the minimum platform/user behavior needed to prove the plugin flow:
NURTURE → ROAM → DIALOGUE → REPORT
Harness outputs are written to test/plugin-harness/output/ and are ignored by git.
Full prototype verification
When this repository is checked out as the ClawLove-S2W2 submodule inside the full ClawLove source tree, run the parent verification command:
cd /path/to/clawLove
npm run prototype:verify
That command runs backend tests, the Sweetheart happy-path harness, miniprogram tests, and miniprogram contract tests.
Evidence to report
A third-party verification report should include:
- S2W2 commit hash.
- Parent repository commit hash when tested as a submodule.
- Exact command used.
- Pass/fail console output.
- Hash of any generated verification report, if produced by the parent harness.
Non-goals
This delivery does not expose full internal product design, production infrastructure, private issue history, real credentials, or generated test workspaces. It is a minimal executable prototype package for feasibility validation.