weichen dbdb47ed09 Make boolean column reads and writes work on both storage tiers
Why:
The dev runtime switched to the PostgreSQL tier today and every
conversation endpoint started returning 500. Migrations define
conversations.pinned/archived/allow_cross_read/cross_private and
users.must_change_password/is_admin as BOOLEAN on PostgreSQL but
INTEGER on SQLite, while the store layer compared them with 0/1
literals, scanned them into int, and wrote them via boolInt().
Under pgx these fail with 42883 (operator does not exist: boolean =
integer), bool encode errors, or 42804 (column is of type boolean but
expression is of type integer).

Evidence:
- main 4fd03ee with AGENT_PG_TEST_DSN: TestConversationFlagsAndTaskList
  and TestAdminAccountsAndSessions fail with the errors above; live
  GET /api/conversations returned "operator does not exist: boolean =
  integer (SQLSTATE 42883)".
- this branch: full ./internal/store suite green on the PostgreSQL tier
  (AGENT_PG_TEST_DSN against a scratch database), pgbus green,
  make test-backend green on the SQLite tier.
- scan into *bool and Go bool parameters are cross-dialect: pgx encodes
  bool natively; database/sql converts bool<->0/1 for SQLite.
- pre-existing and out of scope: ./internal/runmgr PG integration tests
  fail on main too (gin_trgm_ops invisible inside the search_path
  isolation schema, 42704).

Impact:
Conversations list/detail/flags and user auth-state reads/writes now
work identically on both storage tiers; SQLite behavior is unchanged
(same tests green). Boolean columns that are INTEGER in both dialects
(hitl_cards.resolved, profiles.builtin, activity_cards.pinned) keep
boolInt().

Refs: task card .task/fix-pg-boolean-columns.md
2026-10-04 14:51:28 +00:00

Agent-System-Dev

Agent-System 的开发集成仓(父仓):以 submodule 固定全部模块组合,承载跨仓构建、测试编排与原生(非容器)开发环境。非分发单元——发布物在 Agent-System-Releases。

组合结构

modules/core        Agent-System-Core        核心契约(领域模型/事件协议/插件 API/设置与 UI 词汇)
modules/backend     Agent-System-Backend     后端单二进制(内嵌前端与嵌入式 SQLite)
modules/frontend    Agent-System-Frontend    前端(React 19 + Vite + TS)
modules/documents   Agent-System-Documents   系统文档与过程记录
modules/ui          Agent-System-UI          UI 组件库(词汇渲染器/设计令牌/收件箱卡片工作区组件)
deps/development-guidelines                 开发规范(gitlink 固定版本)
deps/agent-native  deps/agent-squad  deps/agent-intent   生态执行/编排/意图
deps/agent-command   Agent-Command           命令总线基础库(spec/注册表/危险分级/审计信封)
deps/error-code-system  deps/logging-system   基础设施
plugins/            示例插件与插件开发参考(P4 起填充)

父仓 gitlink 是各组件源码版本的权威;构建、审核与发布固定提交,不执行 submodule update --remote。

常用命令

make sync     # 物化全部 submodule(递归)
make build    # 构建单二进制 bin/agent-system
make test     # 全量测试
make dev      # 开发模式说明(前后端分离热更新)

约束(全局)

  • 非容器化部署:默认单二进制,必要时拆分多个原生二进制;不发布容器镜像。
  • 依赖方向:frontend→core←backend;插件只依赖 core;生态仓依赖纪律沿用各仓既有约定。
  • 开发规范:deps/development-guidelines(见各仓 AGENTS.md)。

文档

设计方案:modules/documents/docs/proposals/2026-09-29-system-skeleton-design-and-plan.md(含 D1–D16 决策记录)。 本机服务管理(后端/前端/数据库部署、生命周期、备份克隆):docs/svc.md(scripts/svc.sh)。

S
Description
开发集成仓:以 submodule 固定全部模块组合,承载跨仓构建、测试编排与原生(非容器)开发环境;发布物在 Agent-System-Releases。
Readme
29 MiB
Languages
Python 56.2%
Shell 35.9%
Go 5.3%
JavaScript 1.4%
Makefile 1.1%
Other 0.1%