Quality improvement

[ar4ntic]

Note

Medium Risk
Changes sync/import and doctor behavior (symlinks rejected, size limits) and adapter JSON-RPC framing; mostly defensive but can alter repos that relied on symlinks or very large adapter messages.

Overview
Releases 0.1.2 and ignores .ai/ and agentmesh.lock in git.

Hardens filesystem and adapter I/O: entity trees reject symlinks and enforce depth/file-count/size caps; imports use symlink_metadata and skip symlinked paths with explicit reasons. JSON-RPC stdio now caps frames at 64 MiB before allocating bodies. Shared SDK gains collect_entity_files, is_regular_file/dir, and frontmatter moved to its own module; Claude/Codex hook install/remove live in dedicated hooks modules.

Doctor logic moves to pipeline/doctor.rs and adds lockfile privacy heuristics (sensitive ids, paths, override keys) surfaced in DoctorHealth.lockfile_privacy_warnings. jsonschema drops default features (smaller lockfile). Watcher service registration splits into service.rs. CI runs installers/test-install.sh.

^{Reviewed by Cursor Bugbot for commit efbb5a3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b6a807d. Configure here.}

[cursor]

Entity limit constants duplicated across two crates

Low Severity

MAX_ENTITY_TREE_DEPTH, MAX_ENTITY_FILE_COUNT, and MAX_ENTITY_TOTAL_BYTES are identically defined in both agentmesh-adapter-sdk-rust and agentmesh-core. Both crates depend on agentmesh-protocol, which already hosts shared constants like MAX_FRAME_BYTES. These limits enforce the same conceptual constraint on entity trees and could silently drift if only one copy is updated.

Additional Locations (1)

• crates/agentmesh-adapter-sdk-rust/src/lib.rs#L28-L31

 

^{Reviewed by Cursor Bugbot for commit b6a807d. Configure here.}