fix(ports): reassign cipher_memory 8096→8105 — claws, TAC trees, agent-teams configs

[POWERFULMOVES]

Summary

PR B following #1344 — updates config files referencing cipher-memory at port 8096.

Files Changed (19)

Category	Count	Files
CLAWS opencode JSON	5	kvm4-2, 4090, 5090, kvm4-1, nemotron-claw
CLAWS scopes JSON	6	kvm4-2, 4090, 5090, kvm4-1, nemotron-claw, z890
CLAWS claude-md	4	kvm4-2, kvm4-1, 4090 (2 refs), 5090
TAC trees	3	agent-teams-taxonomy, mcp-topology (7 refs), firefly-iii
Agent teams	1	agent-teams.yaml

Verification

grep -rn cipher.memory:8096|cipher-memory:8096 pmoves/configs/ → zero results.

Not Changed (intentional)

• Headscale 8096, jellyfin 8096, consciousness-service 8096, HF MCP 8096

Follow-up

• PR C: documentation files (docs/, research/, pbnj/)
• Submodule PR: pmoves-cipher-mcp/ default URL

[coderabbitai]

Warning

Rate limit exceeded

@POWERFULMOVES has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 50 minutes and 50 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 50 minutes and 50 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3c77d9ba-8227-4e00-812b-4a6e2846f72c

📥 Commits

Reviewing files that changed from the base of the PR and between 3e23183 and 35e0dbc.

📒 Files selected for processing (19)

• pmoves/configs/agent-teams.yaml
• pmoves/configs/claws/claude-md/4090.md
• pmoves/configs/claws/claude-md/5090.md
• pmoves/configs/claws/claude-md/kvm4-1.md
• pmoves/configs/claws/claude-md/kvm4-2.md
• pmoves/configs/claws/opencode-4090.json
• pmoves/configs/claws/opencode-5090.json
• pmoves/configs/claws/opencode-kvm4-1.json
• pmoves/configs/claws/opencode-kvm4-2.json
• pmoves/configs/claws/opencode-nemotron-claw.json
• pmoves/configs/claws/scopes/4090.json
• pmoves/configs/claws/scopes/5090.json
• pmoves/configs/claws/scopes/kvm4-1.json
• pmoves/configs/claws/scopes/kvm4-2.json
• pmoves/configs/claws/scopes/nemotron-claw.json
• pmoves/configs/claws/scopes/z890.json
• pmoves/configs/tac_trees/agent-teams-taxonomy.tac.yaml
• pmoves/configs/tac_trees/firefly-iii.tac.yaml
• pmoves/configs/tac_trees/mcp-topology.tac.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/cipher-memory-port-8096-to-8105-configs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 35e0dbc454

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Point Cipher MCP URL at currently exposed port

This change moves the CLAWS Cipher endpoint to :8105, but the runtime defaults still expose Cipher on :8096 (pmoves/docker-compose.yml uses ${CIPHER_PORT:-8096}:3000, and related health checks/default URLs still use 8096). In any default environment where CIPHER_PORT is not explicitly overridden, clients loading this config will fail to connect to Cipher Memory, so memory-backed tooling regresses immediately.

Useful? React with 👍 / 👎.