You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c8320ce
Browse filesBrowse the repository at this point in the historyBrowse files
Merge sync/upstream-step2 into step 4: test fixes, legacy-block warning, output budget
Brings the Jenkins-green step-2 line (release-tooling DeusData#60, 904ae6b) into the
fully merged step-4 tree:
- 12 step-2 tests aligned with the CLI-only fork (cc9f002)
- feat/legacy-mcp-block-warning: install and uninstall warn about leftover
codebase-memory-mcp instruction blocks and leave them in place
- feat/output-token-budget: max_output_tokens for search_code, trace_path
and detect_changes, plus match_limit, source_max_lines and directory
paging
- lint fixes and memory-core baseline notes (904ae6b)
Conflicts:
- tests/test_daemon_application.c, over-budget passthrough. Kept step 2's
binary-safe app_test_response_contains instead of strstr on a binary
frame. Searches the whole frame and accepts either error-flag spelling:
is_error from the operation result wire on this tree, isError from a
passed-through body.
- scripts/memory-core-baseline.txt regenerated for the merged tree. These
are counts the fork already had, not new raw allocations.
Validated locally:
- `scripts/build-dev.sh` and the test-runner compile are clean with
-Werror.
- `scripts/lint.sh --ci` passes.
- Vendored checksums verify.
Copy file name to clipboardExpand all lines: docs/CONFIGURATION.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -219,7 +219,7 @@ not name is permitted.
219
219
220
220
## 5. Agent and Editor Integration Files
221
221
222
-
The CLI-first `install` path can write Codebase Memory skills and durable CLI instructions for detected agents. Hooks are a separate explicit opt-in via `codebase-memory-cli install-hooks`. Neither lifecycle surface creates, migrates, adopts, or removes MCP registrations or MCP-owned assets; existing MCP state is treated as foreign for side-by-side safety.
222
+
The CLI-first `install` path can write Codebase Memory skills and durable CLI instructions for detected agents. Hooks are a separate explicit opt-in via `codebase-memory-cli install-hooks`. Neither lifecycle surface creates, migrates, adopts, or removes MCP registrations or MCP-owned assets; existing MCP state is treated as foreign for side-by-side safety. Both `install` and `uninstall` warn when an instruction file still contains a legacy `codebase-memory-mcp` managed block from the upstream MCP tool, but they leave that block in place for you to remove by hand.
223
223
224
224
Those target paths vary by tool and platform, so the easiest way to inspect the exact files for your machine is:
0 commit comments