cocoplus-config

Objective

cocoplus.toml is the single source of truth for all operator-configurable plugin settings. This skill handles two commands:

• $cocoplus sync — propagates cocoplus.toml into downstream artifacts
• $cocoplus migrate-config — converts legacy safety-config.json to cocoplus.toml

Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus is not initialized. Run $pod init first." Then stop.

---

Command: $cocoplus sync

Step 1 — Read cocoplus.toml

Read cocoplus.toml from the project root. If absent, output:

cocoplus sync: cocoplus.toml not found.
Run $pod init to create a project bundle (which generates cocoplus.toml), or create cocoplus.toml manually using templates/cocoplus.toml.template from the installed CocoPlus plugin bundle.

Then stop.

Parse the TOML. If it contains a syntax error, output: "cocoplus sync: cocoplus.toml has a syntax error — [description]. Fix the file and re-run $cocoplus sync." Then stop.

Step 2 — Read Existing Sync Manifest

Read .cocoplus/config/sync-manifest.json if it exists. Record file_hashes from the last sync for drift detection.

Step 3 — Drift Detection

For each file listed in the prior sync manifest, check whether the file's current content hash matches the recorded hash. If any file was manually edited since the last sync, collect the list and warn:

cocoplus sync: The following generated files were modified since the last sync:
  - hooks/the PreToolUse hook  (modified 2024-01-22)
These changes will be overwritten. Edit cocoplus.toml instead.

Proceed with overwrite regardless — generated files are controlled by cocoplus.toml.

Step 4 — Regenerate Pre-Tool-Use Security Rules

Read the [security] section from cocoplus.toml:

• always_allow — list of tool/operation patterns always permitted
• ask_first — list requiring confirmation
• human_required — list requiring explicit human approval
• never — list unconditionally blocked

Update the boundary_tiers configuration in .cocoplus/config/security-rules.json: