0 Fork 0

mirror of https://github.com/Ed1s0nZ/CyberStrikeAI.git synced 2026-11-13 15:57:22 +01:00

Files

T

Sycun 35508eb614 feat(pi): add the Pi agent runtime with native workflow and retrieval engines

Introduce an isolated Node worker that hosts the Pi SDK while Go keeps
business state, permissions, MCP execution, evidence and delivery checks.
The worker is published per source fingerprint, streams events back to Go
and supports tool callbacks, cancellation, session resume and per-model
transport settings.

Agent dispatch, tool search, plan/task tools and migration controls are
wired on top of it: large tool catalogs load through Pi tool_search, the
conversation task board keeps its existing tools, and legacy mode/route
values still resolve. Workflow gains a native DAG with versioned JSON
checkpoints, and knowledge retrieval moves to native documents, splitter,
HTTP embeddings, vector search and reranking.

2026-11-12 17:55:33 +08:00

1.8 KiB

Raw Blame History

Release Process

中文

Use this guide for maintainers and operators preparing upgrades or releases.

Pre-Release Checklist

README and docs updated.
config.yaml sample includes new fields.
OpenAPI includes new endpoints.
i18n updated when frontend text changed.
Security docs updated for high-risk capabilities.

Release Risk Tiers

Change	Risk	Must test
Docs/assets	low	links/rendering
Frontend	medium	login, page states, API errors
Handler/API	medium	OpenAPI, auth, errors
Config struct	high	old config compatibility, ApplyConfig
DB schema	high	old DB migration, rollback
Agent/MCP/HITL	high	tools, approvals, streaming
C2/WebShell/Terminal	critical	authorized lab, audit, disable switch

Release notes should call out risk, not just features.

Config Compatibility

New fields should:

have safe defaults;
allow old configs to start;
be documented in sample config.yaml;
not cause Web settings to delete unknown fields;
be tested via restart and hot-apply paths.

Avoid default-enabling high-risk capabilities.

Database Changes

SQLite migrations must be:

compatible with old versions;
idempotent after interruption;
careful with nullable/default fields;
mindful of large indexes and locks;
documented with backup instructions.

Build and Test

go test ./internal/...
go test ./cmd/...
bash scripts/build-pi-runtime.sh
go build -o cyberstrike-ai ./cmd/server

Manual smoke:

login -> model test -> new chat -> tools -> HITL -> KB -> external MCP -> C2 enable/disable

Rollback

Restore binary/code, config.yaml, and data/ together. If a new version changed DB schema, replacing only the binary is not a reliable rollback.

1.8 KiB Raw Blame History