docs/beads-reference.md (1)

757-762: Minor: Add language specifiers to fenced code blocks.

The hierarchy examples and quick reference card lack language specifiers, triggering markdownlint MD040 warnings. Consider adding text or plaintext for better accessibility and syntax highlighting support.

Also applies to: 766-772, 840-878

🤖 Prompt for AI Agents

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

In `@docs/beads-reference.md` around lines 757 - 762, The fenced code blocks that
show the task hierarchy (the block starting with "root task (in_progress)" and
similar quick-reference examples) are missing language specifiers and trigger
markdownlint MD040; update each triple-backtick fence for these examples
(including the hierarchy blocks and the quick reference card examples) to use a
neutral specifier such as ```text or ```plaintext so they are explicitly flagged
as plain text for syntax highlighting and accessibility.

tools/harbor_agent/proto_agent.py (1)

116-124: Consider adding checksum verification for the downloaded binary.

The installation fetches a pre-built binary from GitHub without verifying its integrity. While the version is pinned, adding a SHA256 checksum verification would improve supply chain security.

🔒 Proposed fix with checksum verification

         await self.exec_as_root(
             environment,
             command=(
                 "BR_VERSION=v0.1.35 && "
+                "BR_SHA256=<expected-sha256-here> && "
                 "curl -fsSL https://github.com/Dicklesworthstone/beads_rust/releases/download/${BR_VERSION}/"
-                "br-${BR_VERSION}-linux_amd64.tar.gz | tar -xz -C /usr/local/bin && "
+                "br-${BR_VERSION}-linux_amd64.tar.gz -o /tmp/br.tar.gz && "
+                "echo \"${BR_SHA256}  /tmp/br.tar.gz\" | sha256sum -c - && "
+                "tar -xzf /tmp/br.tar.gz -C /usr/local/bin && "
+                "rm /tmp/br.tar.gz && "
                 "chmod +x /usr/local/bin/br && br --version || echo 'beads_rust install failed (non-fatal)'"
             ),
         )

🤖 Prompt for AI Agents

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

In `@tools/harbor_agent/proto_agent.py` around lines 116 - 124, The install
command invoked via exec_as_root should verify the downloaded archive's SHA256
before extraction: fetch the release tarball and the expected checksum (or
include a pinned SHA256 value) and run sha256sum (or openssl dgst -sha256) to
compare the computed digest against the expected one, failing the install if
they don't match; update the command string passed to exec_as_root (the command
in proto_agent.py that uses BR_VERSION to curl the tarball) to first download
the checksum or embed the pinned checksum, verify the file, then extract and
chmod only if verification succeeds, and ensure any temporary files are removed
on success/failure.

packages/core/src/tools/task-ready.ts (1)

44-53: Consider extracting shared priority mapping constant.

The priority mapping duplicates PRIORITY_TO_BR from task-store.ts. While the duplication is minor and unlikely to diverge, consider extracting to a shared location if this mapping is needed elsewhere.

♻️ Potential shared constant

Create a shared constants file or export from task-store.ts:

// In a shared location (e.g., task-constants.ts)
export const PROTO_PRIORITY_TO_BR: Record<string, string> = {
  critical: '0',
  high: '1', 
  medium: '2',
  low: '3',
};

🤖 Prompt for AI Agents

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

In `@packages/core/src/tools/task-ready.ts` around lines 44 - 53, Extract the
duplicated priority mapping from task-ready.ts (the local priorityMap used with
this.params.priority and args.push('--priority', p)) into a shared exported
constant (e.g., PROTO_PRIORITY_TO_BR) and import that constant instead of
redefining it, aligning it with the existing PRIORITY_TO_BR in task-store.ts so
both task-ready.ts and task-store.ts reference the same shared symbol to avoid
duplication.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes