feat: register generated apps with agent harness

This commit is contained in:
2026-08-07 16:31:39 +09:00
parent c99b0ebf8a
commit c5acb77449
13 changed files with 102 additions and 16 deletions

View File

@@ -9,7 +9,7 @@
### Generated Backend Invariants
- Generated applications use Java 17, Spring Boot 3.5.7, the repository Gradle Wrapper, and `com.kri.common:starter:beta.1.6.3`.
- Generated applications use Java 17, Spring Boot 3.5.7, the repository Gradle Wrapper, and `com.kri.common:starter:beta.1.6.4`.
- Keep the approved KriCommon version exact. Do not restore `latest.release` or another dynamic version.
- Preserve the selected MySQL or MSSQL driver, profile configuration, JPA/QueryDSL structure, and optional MyBatis template behavior.
- Generate `.agent/profile.yml`, `.agent/project.md`, and harness line-ending policy for every project. Never copy a stale precomposed `AGENTS.md` into the template.
@@ -18,7 +18,7 @@
- Generated projects default to `requested-project`; allow the supported explicit project-type override without changing the fixed `backend` layer.
- Include the selected database in the generated profile and declare consumption of the KriCommon contract.
- When the central harness is available, register the project locally and run compose followed by verify. Central-harness absence must not prevent project creation.
- When the central harness is available, register the project in shared `workspace.yml` by default and run compose followed by verify. Allow an explicit local-registration override, and do not perform Git commits. Central-harness absence must not prevent project creation.
- `AGENTS.md` and `CLAUDE.md` in this repository are harness-generated outputs. Never edit either file directly; edit `.agent` sources and recompose.
- Do not commit user-specific absolute harness paths or credentials. Explicit paths are runtime inputs only.