wangxuming/makelore
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

merge: integrate upstream main with local Makelore changes

Browse Source
This commit is contained in:
inman
2026-08-31 10:55:48 +08:00
parent 62304dc85b 33fb31fb28
commit 28897cd4a2
128 changed files with 8278 additions and 3030 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
AGENTS.md
View File

@@ -26,14 +26,14 @@ Use the exact pnpm version pinned by `packageManager` in `package.json`.
- Do not add direct page/component IPC calls or direct local-runtime HTTP requests.
- Electron Main owns runtime startup, Host API routes, authentication, providers, secrets, synchronization, proxies, updates, and system integration.
- Keep AI programming project state local and project-scoped.
- Keep AI painting behind its Main-owned cloud V2 Workspace contract. One Workspace owns one persistent Living Form and Agent Session; Renderer chat and direct edits must use the same server reducer. Do not add a local semantic adapter or fallback.
- Preserve internal `niancode` compatibility identifiers unless a separately approved migration covers app id, protocol, storage, environment, headers, backend contracts, and installed-user data.
- Keep AI painting behind its Main-owned cloud V2 Workspace contract. One Workspace owns one persistent Living Form and Agent Session; Renderer chat and direct edits must use the same server reducer. The unpackaged local adapter is development-only and must never become a packaged fallback or semantic authority.
- Do not change app id, protocol, global user-data paths, environment variables, request headers, or backend contracts as an incidental part of project-data work.
- Keep the product on the single Makelore light visual system. Do not add a dark-theme product mode.
## Agent and project configuration
- Project configuration is authoritative in `.niancode/project.json`.
- Agent definitions are project-owned in `.niancode/project.json`; Pi runtime
- Project configuration is authoritative in `.makelore/project.json`; do not read or migrate project metadata from `.niancode` or `.opencode`.
- Agent definitions are project-owned in `.makelore/project.json`; Pi runtime
state must not become an alternative source of project configuration.
- Stable Agent ids preserve sessions; display names are editable.
- Do not refactor Agent templates, prompts, or the Coding/Pi structure as an incidental part of unrelated work.