Skip to content

feat: fx adoption baseline, LSP enablement, and extension trust status - #223

Merged
Patel230 merged 7 commits into
mainfrom
fix/enable-lsp-and-close-adoption-checklist
Aug 22, 2026
Merged

feat: fx adoption baseline, LSP enablement, and extension trust status#223
Patel230 merged 7 commits into
mainfrom
fix/enable-lsp-and-close-adoption-checklist

Conversation

@Patel230

Copy link
Copy Markdown
Contributor

Summary

Completes the Vercel fx adoption plan plus Kimi Code workflow parity:

  • Kimi Code adoption: distinct planner/explorer model roles, Kimi-compatible hook lifecycle events, adoption plan docs
  • fx P0: stable-ID exact permission rules with hawk permissions add/list/revoke/reset, atomic persistence, reset generation protection
  • fx P0: project settings authority boundaries — .hawk/settings.json can no longer override provider/model, permission grants, MCP servers, custom providers, or thinking settings
  • Unified redacted status: internal/status snapshot wired into hawk status [--json], daemon GET /v1/status, and ACP session/status; OpenAPI updated
  • Subagent observability: child sessions surfaced in ACP status
  • LSP fix: subprocess LSP manager wired into the primary chat tool registry (lazy start); diagnostics/definition/references/symbols route through configured language servers with codegraph/local-tool fallbacks
  • Extension trust UX: MCP/skills state and trust warnings in status snapshots

Test plan

  • Full go test ./... passes (run twice, including via pre-push hooks)
  • make vet, make lint clean
  • hawk verify passed (security log verified)
  • Boundary guards + external-drift + govulncheck passed in pre-push hooks

@Patel230
Patel230 merged commit ef9a0fd into main Aug 22, 2026
26 checks passed
@Patel230
Patel230 deleted the fix/enable-lsp-and-close-adoption-checklist branch August 22, 2026 02:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant