Release v2.2.0 (Container) + v0.2.0 (CLI)

[AnExiledDev]

Summary

• @coredirective/cf-container v2.2.0 — Claude Code Router, Codex CLI, 6 new behavioral rules, agent model upgrades, config tuning, docs restructure
• @coredirective/cf-cli v0.2.0 — session tokens command for thinking token analysis

Container Highlights

• Claude Code Router — proxy daemon for routing API calls to alternate LLM providers (DeepSeek, Gemini, OpenRouter)
• Codex CLI — OpenAI terminal coding agent with config management and persistence
• New rules — auto-memory, zero-tolerance-bugs, scope-discipline, explicit-start, plan-presentation, surface-decisions
• Agent system — all opus-based agents pinned to opus-4-5, investigator/security-auditor upgraded to opus
• Config changes — Opus 4.7 default, thinking tokens reduced, effort level max, compaction tuned

CLI Highlights

• codeforge session tokens — analyze thinking token usage across sessions with density metrics

Test plan

• CLI tests pass (327 tests)
• Container tests pass (updated for new config location)

Summary by CodeRabbit

• Tests
  • Updated validation tests to confirm CodeForge assets are properly organized in the new default location
  • Tests now verify required configuration and manifest files are present in expected locations
  • Removed obsolete synchronization checks between separate asset directories
  • Strengthened validation to focus on default directory structure integrity

[coderabbitai]

📝 Walkthrough

Walkthrough

The test suite was updated to validate CodeForge assets at a new defaults directory path (.devcontainer/defaults/codeforge/) instead of .codeforge/. Test validation logic was modified across Tests 3, 7, and 8, shifting from checksum equality comparison to directory structure verification.

Changes

Cohort / File(s)

Summary

Test Suite Path Migration container/test.js

Updated Tests 3, 7, and 8 to validate CodeForge assets in new defaults path. Test 3 expects required files in new location. Test 7 checks defaults directory existence and runs checksum generation there. Test 8 rewritten to verify directory structure and specific files instead of comparing checksums between directories. Final validation condition changed from bundledDefaultsInSync to defaultsStructureValid.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 Paths shift and tests align,
New defaults in containers fine,
Checksums yield to structure's call,
CodeForge assets stand up tall!
Validation hops to .devcontainer way,
Tests pass brighter every day! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title references version releases (v2.2.0 Container, v0.2.0 CLI) which align with the PR's purpose of publishing major releases, though it is broad rather than highlighting the specific primary change.
Description check	✅ Passed	The PR description covers the main changes, test plan status, and feature highlights for both Container and CLI releases. It follows the general spirit of the template with summary/highlights instead of the prescribed sections, missing formal Type of Change checkboxes and Changelog/Documentation update confirmations.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch staging

---

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.}

[coderabbitai]

🧹 Nitpick comments (2)

container/test.js (2)

100-137: Minor: consolidate the defaultsDir existence check.

Tests 7 and 8 both check fs.existsSync(defaultsDir) and emit separate "not found" messages. Consider guarding once up front (or extracting a helper) to avoid duplicated branches and failure messages.

Example consolidation

-	if (fs.existsSync(defaultsDir)) {
-		const checksums = generateChecksums(defaultsDir);
-		...
-	} else {
-		console.log("❌ Test 7: .devcontainer/defaults/codeforge/ not found, skipping");
-		checksumStructureValid = false;
-	}
+	const defaultsExists = fs.existsSync(defaultsDir);
+	if (!defaultsExists) {
+		console.log("❌ Tests 7-8: .devcontainer/defaults/codeforge/ not found");
+		checksumStructureValid = false;
+		defaultsStructureValid = false;
+	} else {
+		// run Test 7 and Test 8 bodies
+	}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@container/test.js` around lines 100 - 137, Consolidate the duplicated
existence check for defaultsDir by guarding once before running Test 7 (and Test
8) so you only call fs.existsSync(defaultsDir) a single time; if the directory
is missing, emit one clear "not found" message and set the relevant test flags
(e.g., checksumStructureValid) accordingly, otherwise run
generateChecksums(defaultsDir) and the existing validation logic (checks for
object, non-empty keys, and 64-char SHA-256 hex strings) for the tests; update
references to defaultsDir, generateChecksums, and checksumStructureValid to use
this single branch or extract a small helper that performs the exists check and
returns the checksums to avoid duplicated branches and messages.

---

139-168: Test 8 coverage weakened — consider keeping a sync/integrity check.

The previous Test 8 compared checksums between a source .codeforge/ and the bundled defaults to catch drift. The rewrite only asserts that config/, file-manifest.json, and config/settings.json exist, which will pass even if the manifest is out of sync with actual file contents, or if other expected files under defaults/codeforge/ are missing/corrupted.

If there's still a canonical source for bundled defaults (or a manifest enumerating expected files), consider validating against it instead of a hardcoded 2-file list, so regressions in the packaged defaults are still caught.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@container/test.js` around lines 139 - 168, Test 8's current check (using
defaultsStructureValid, expectedSubdirs, expectedFiles and defaultsDir) only
verifies presence of a couple files; update it to validate integrity against the
canonical manifest or source: read the canonical file-manifest.json (or the
upstream .codeforge/ directory if available), iterate the manifest entries and
for each expected path verify existence and checksum/hash matches (or compare
file contents against the source copy), and fail (set defaultsStructureValid =
false and log) on any mismatch so the test detects drift rather than only
missing files.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@container/test.js`:
- Around line 100-137: Consolidate the duplicated existence check for
defaultsDir by guarding once before running Test 7 (and Test 8) so you only call
fs.existsSync(defaultsDir) a single time; if the directory is missing, emit one
clear "not found" message and set the relevant test flags (e.g.,
checksumStructureValid) accordingly, otherwise run
generateChecksums(defaultsDir) and the existing validation logic (checks for
object, non-empty keys, and 64-char SHA-256 hex strings) for the tests; update
references to defaultsDir, generateChecksums, and checksumStructureValid to use
this single branch or extract a small helper that performs the exists check and
returns the checksums to avoid duplicated branches and messages.
- Around line 139-168: Test 8's current check (using defaultsStructureValid,
expectedSubdirs, expectedFiles and defaultsDir) only verifies presence of a
couple files; update it to validate integrity against the canonical manifest or
source: read the canonical file-manifest.json (or the upstream .codeforge/
directory if available), iterate the manifest entries and for each expected path
verify existence and checksum/hash matches (or compare file contents against the
source copy), and fail (set defaultsStructureValid = false and log) on any
mismatch so the test detects drift rather than only missing files.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9f17f58b-57d8-405b-aeab-e9dfdfad753b

📥 Commits

Reviewing files that changed from the base of the PR and between 6824462 and 05d772d.

📒 Files selected for processing (1)

• container/test.js