sync: merge upstream v1.0.131

[shuv1337]

Summary

• Merges upstream sst/opencode v1.0.131 changes into the shuvcode fork
• Resolves all merge conflicts following the established conflict resolution strategy

Resolved Conflicts

File	Resolution
AGENTS.md	Keep ours (fork-specific instructions)
bun.lock	Regenerated with bun install
packages/opencode/script/build.ts	Keep ours (shuvcode naming + OPENCODE_BASE_VERSION)
packages/opencode/src/session/index.ts	Accept upstream (safer cache?.read optional chaining)
packages/opencode/src/session/processor.ts	Keep ours (Token import)
packages/opencode/src/tool/task.ts	Keep ours (Wildcard + filterSubagents)
packages/console/app/src/routes/workspace/[id]/graph-section.tsx	Accept upstream pattern
package.json files	Accept upstream versions (1.0.131)
packages/extensions/zed/extension.toml	Accept upstream versions (1.0.131)

Validation

• Typecheck: Passed
• Tests: 264 passed, 1 skipped, 0 failed

Closes #83

Summary by CodeRabbit

• Chores

  • Released version 1.0.131 across all packages.
  • Removed unused dependency.

• Bug Fixes

  • Fixed potential runtime errors in data access operations.

• Improvements

  • Enhanced graph section data loading with improved state management and responsiveness.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Release version bump from 1.0.130 to 1.0.131 across multiple packages and configuration files. Includes refactoring of graph-section component data loading to use effect-based reactive flow, optional chaining safety improvements, and removal of an unused dependency.

Changes

Cohort / File(s)	Change Summary
Version Bumps (Package.json) packages/console/app/package.json, packages/console/core/package.json, packages/console/function/package.json, packages/console/mail/package.json, packages/desktop/package.json, packages/enterprise/package.json, packages/function/package.json, packages/plugin/package.json, packages/sdk/js/package.json, packages/slack/package.json, packages/tauri/package.json, packages/ui/package.json, packages/util/package.json, packages/web/package.json, sdks/vscode/package.json	Version incremented from 1.0.130 to 1.0.131 across all packages.
Release Tag and Configuration .github/last-synced-tag, packages/extensions/zed/extension.toml	Updated sync tag from v1.0.130 to v1.0.131; Zed extension version and platform-specific release URLs updated to v1.0.131.
Graph Section Refactoring packages/console/app/src/routes/workspace/[id]/graph-section.tsx	Reworked data loading from initialData/queryCosts to effect-based reactive flow with getCosts(); removed server-side color-scheme initialization in favor of client-side effect; simplified navigation to update store only; refactored chart data source and filtering UI; added chart cleanup logic.
Optional Chaining and Dependency Updates packages/opencode/package.json, packages/opencode/src/session/index.ts	Removed opentui-ansi-vt dependency; applied optional chaining (?.) to costInfo.cache property access for safer undefined handling.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

• Primary focus areas:
  • packages/console/app/src/routes/workspace/[id]/graph-section.tsx: Verify effect-based data loading logic and chart lifecycle management, especially onCleanup behavior
  • Confirm optional chaining changes in packages/opencode/src/session/index.ts correctly handle undefined cache scenarios
  • Validate removal of opentui-ansi-vt dependency has no downstream impact in the opencode package
• Lower effort items: Version bump consistency and URL updates across extensions and manifests are straightforward to verify

Poem

🐰 A leap to v1.0.131, hooray!
Data flows reactively today,
Effects and stores dance in sync,
Optional chains prevent the brink,
Version bumps in every way! ✨

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch opencode/issue83-20251204041504

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1984fae and ed09d72.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (20)

• .github/last-synced-tag (1 hunks)
• packages/console/app/package.json (1 hunks)
• packages/console/app/src/routes/workspace/[id]/graph-section.tsx (5 hunks)
• packages/console/core/package.json (1 hunks)
• packages/console/function/package.json (1 hunks)
• packages/console/mail/package.json (1 hunks)
• packages/desktop/package.json (1 hunks)
• packages/enterprise/package.json (1 hunks)
• packages/extensions/zed/extension.toml (2 hunks)
• packages/function/package.json (1 hunks)
• packages/opencode/package.json (1 hunks)
• packages/opencode/src/session/index.ts (1 hunks)
• packages/plugin/package.json (2 hunks)
• packages/sdk/js/package.json (2 hunks)
• packages/slack/package.json (1 hunks)
• packages/tauri/package.json (1 hunks)
• packages/ui/package.json (1 hunks)
• packages/util/package.json (1 hunks)
• packages/web/package.json (1 hunks)
• sdks/vscode/package.json (1 hunks)

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

https://github.com/Latitudes-Dev/shuvcode/blob/ed09d7236df328f396e41112561e52f01c864482/packages/console/app/src/routes/workspace/[id]/graph-section.tsx#L206-L210
Restore SSR guard around DOM access

The chart config memo now hits getComputedStyle(document.documentElement) without the previous if (typeof window === "undefined") return null guard, so server-side rendering this route will throw ReferenceError: document is not defined before any data loads. The console app renders on the server, so any SSR render or test that imports this component will crash until the DOM access is gated to the client.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".