chore: add .opencode/dcp.jsonc with compress.protectTags enabled

Open Beginner friendly
#77 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
json
Domain
tooling

Research direction

Read opencode.json and check where protectTags is currently set. Remove that top-level key and add .opencode/dcp.jsonc with the schema URL and compress.protectTags setting shown in the issue. Done means the DCP setting is in the project-level config and the invalid key is no longer in opencode.json.

Written by the indexing model from the issue text.

Description

Problem

Slash command files use <protect> tags to mark execution-critical sections (guardrails, checklists, mandatory gates) that must survive DCP context compression. However, these tags are inert without a DCP config file that enables them.

Additionally, the replicator repo currently has "protectTags": true at the top level of opencode.json, which causes:

Configuration is invalid at opencode.json
↳ Unrecognized key: protectTags

Fix

  1. Remove "protectTags": true from opencode.json
  2. Add .opencode/dcp.jsonc to the repo with:
{
  "$schema": "https://raw.githubusercontent.com/Opencode-DCP/opencode-dynamic-context-pruning/master/dcp.schema.json",
  "compress": {
    "protectTags": true
  }
}

This file should be committed to source control (project-level setting, not personal config).

Context

  • protectTags is a DCP plugin config key under compress, not an OpenCode core config key
  • Placing it in opencode.json causes the startup error shown above
  • The correct location is .opencode/dcp.jsonc (or dcp.json)
  • Related: unbound-force/unbound-force#497, unbound-force/unbound-force#499
Dominant language
Go
Stars
0
Forks
9
Avg merge
1d 14h
Merged PRs (30d)
18

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from unbound-force/replicator

All issues in unbound-force/replicator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.