Tasks

The agent incorrectly changed the official repository name from savanna-vet-go to savanna in README.md badge URLs and installation/build instructions while adding go vet documentation.

The agent prematurely declared that GPG signing required a manual commit instead of retrying the requested git commit outside the sandbox.

After bumping to v1.3.8, the agent left src/pages/content/changelog/notes/1.3.8.md missing and asked the user to supply release notes instead of generating concise notes from commits and code changes.

The timeline resize implementation narrowed the structural bar, squeezing its nodes, and coupled background fading to width instead of changing only the background width.

The version badge in src/pages/content/prompt/index.ts still navigated to GitHub releases instead of always opening the in-page changelog modal.

frontend/src/components/ContextTreeView.tsx used Chakra UI's styled TreeView without a ChakraProvider, causing Tree view to crash with an undefined-context error.

The /api/v1/query/search implementation still returned no results for class GitHubRepo(BaseModel) because it searched the whole declaration as a phrase or node-name substring without falling back to file-content search.

The admin navigation buttons were visible but misconfigured: map.html linked Admin Tracks to /api/admin/tracks instead of the uploads page, and admin-users.html required a password query parameter even for a logged-in admin.

The agent edited CLAUDE.md instead of the requested README.md to remove content overlapping with SYSTEM_OVERVIEW.md.

The agent falsely reported production commit 22e5546 as live, dismissing the running commit 3b41105 as cached and suggesting a later container restart instead of verifying completion of the deployment.

The README.md cleanup left the inaccurate tagline claiming that Skill Forge (SKF) was part of the BMad Method ecosystem.

In Reader.tsx, backward navigation left wantsLastPageRef active as chapter preloading increased totalPages, repeatedly moving the reader to the end of all loaded chapters rather than the previous chapter.

The expanded streaming rendering branch in MessageBubble.tsx reached an unguarded message.segments!.filter(...) on line 413 when segments was undefined, crashing the frontend.

The memory details modal displayed raw source with the selected entry highlighted instead of Preview/Source tabs matching the skills details modal.

The GitHub link in frontend/src/components/Sidebar.tsx used hard-coded "View on GitHub" text instead of localized title and aria-label attributes.

The agent changed .claude/skills/code-review/SKILL.md to invoke vibx get-intents without adding a matching Bash permission, causing noninteractive reviews to fail the permission check.

The G204 gosec suppression in cmd/entire/cli/git_operations.go falsely claimed that FetchAndCheckoutRemoteBranch's branchName came from existing git refs rather than a user-provided CLI argument.

The resume.go checkpoint search required confirmation or --force after merging main even when no newer branch-work commits followed the checkpoint.

The agent declared the cursor-cli Bootstrap() fix verified after running only static checks, unit tests, and Vogon canary E2E tests, without running real cursor-cli E2E tests locally.

The agent incorrectly described the local branch as enforcing a 1:1 commit-to-session relationship and blocking second sessions, overlooking its existing multi-session storage and functioning concurrent checkpoint hooks.

The agent incorrectly ruled out E2E test-code/setup problems for factoryai-droid, although e2e/agents/droid.go passed unsupported interactive flags instead of configuring model selection through settings.

In strategy/hooks.go, hookCmdPrefix returned the resolved executable path without shell quoting, allowing spaces or shell metacharacters to break generated git hooks or execute unintended commands.

The recommended bench:compare command in mise.toml fed noisy benchmark output to benchstat, producing invalid iteration-count errors, incomplete samples, and poorly formatted branch-comparison tables.

TestCLIVersionInMetadata only checked that cli_version was populated, rather than asserting that its value matched the version of the compiled CLI binary.

The review incorrectly treated agent-integration-checklist.md as an older document being replaced by agent-guide.md, framing differences as requirements lost from the checklist rather than alignment between two retained documents.

The agent recommended storing a CodeCommit hash in checkpoint metadata to find session commit messages, despite commit hashes changing after rebase or amend and Entire-Checkpoint being the stable link.

The agent incorrectly classified an external contributor as a team member and concluded that the release had no external contributors and needed no Thanks section in CHANGELOG.md.

The agent recommended go run ./cmd/entire attach <session-id> even though attach was not registered in cmd/entire/cli/root.go, causing an unknown-command error.

The agent changed Detect() in cmd/entire/cli/agent/registry.go to prefer Claude Code based on directory presence instead of identifying the agent from the incoming agent-specific hook.

The new isGitSequenceOperation() in cmd/entire/cli/strategy/manual_commit_hooks.go duplicated git rev-parse --git-dir logic instead of using GetGitDir(), which normalizes relative paths to absolute paths.

The no-git-repository guard was duplicated in six handlers in hooks_claudecode_handlers.go instead of a shared hook entry point that would also cover future agents.

The agent incorrectly characterized report.nocolor.txt as aspirational and never wired up, overlooking the working report generator in the original entire-cli-e2e-tests repository.

The agent offered manual mcp-chrome-bridger register as the solution instead of fixing the missing automatic Native Host registration during npm install -g mcp-chrome-bridger.

The agent incorrectly claimed all post-card cover images were already clickable after inspecting only PostCard.tsx, overlooking non-clickable images in PostList.tsx and SeriesCatalog.tsx.

The agent explained the build difference only by saying Amytis does not use the reading-time package, without identifying its built-in reading-time calculation that accounts for the demo samples.

The sample collection's prev/next cards used global chronological navigation instead of collection order, and getAllSeries() returned zero parts for its card on the series index.

The agent claimed individual post routes correctly handled autoPaths, but src/app/[slug]/[postSlug]/page.tsx lacked percent-encoded Chinese postSlug variants in generateStaticParams(), causing missing-parameter errors in development with output: export.

The client Dispatch UI edits left a duplicate newTitle state declaration in client/src/App.tsx, causing Vite's React Babel parser to reject the file.

The agent declared .coderabbit.yaml error-free but missed that tone_instructions exceeded CodeRabbit's 250-character limit, causing the configuration to be rejected.

The rewrite of GitHub issue #178 incorrectly required agent runtimes to register their local tools in Brain as mcp_tool nodes with execution_target: "runtime".

The agent relied on stale local master state and proposed merging feature/test-suite-ci-gate even though that branch had already been merged into remote master.

In apps/api/src/logging.ts, RUDEL_LOG_DIR=.context resolved relative to the process working directory, placing logs under apps/api/.context instead of the requested project-root .context.

Gating useAnalyticsQuery.ts with enabled: !!activeOrg?.id left OverviewPage.tsx blank while the organization loaded, despite the agent claiming that kpisLoading would keep the spinner visible.

ProjectTrendChart.tsx rendered ChartLegend without importing it, causing an Uncaught ReferenceError when loading projects.

The agent claimed email/password auth was fully functional, but apps/api/src/index.ts lacked CORS headers for auth routes and credential-enabled CORS for RPC requests from http://localhost:4011.

The agent started rudel-manila-test at http://localhost:3000 without configuring that URL as a trusted auth origin, causing auth requests to return INVALID_ORIGIN.

The agent reported rudel as installed and enabled after bypassing Volta to run enable, while the ordinary rudel command used by .claude/settings.json still failed inside the repository.

The branch review omitted the reproducible developer-experience failure in build-demo-dataset.py where validate_manifest_addressability() rejects the gitignored docs/data/ado-git-repo-insights.sqlite file, treating it as outside the branch's concerns.

In a blog post, the agent asserted without sufficient verification that a person named in a historical account was a particular well-known computer scientist.

The recorded SurrealDB FLEXIBLE guidance was incorrect: migration 0025_policy_condition_union_type.surql used FLEXIBLE TYPE object | array, which SurrealDB rejects because FLEXIBLE must follow TYPE.

The agent claimed all artifacts were loaded while still omitting UX files in docs/ux/agent-learnings/, including the governance-review visual, runtime-injection YAML, and journey feature files.

The agent replaced the existing windows in config/tmuxinator/work.yml and primary.yml with three plain shell tabs instead of preserving the first two windows and adding only a third shell tab.

The agent removed ta and tw without adding the requested two command for a tmux session named work in the fish configuration.

The agent replaced Cmd+Alt+H/J/K/L split-navigation bindings with Cmd+Alt+Arrow keys in config/ghostty/config instead of preserving both sets.

The agent proposed running the cached dev-loop.py script instead of using /dev-loop:workflow to implement default progress logging in StateGraph.run().