yjcli 0.1.4__tar.gz → 0.2.1__tar.gz

{yjcli-0.1.4 → yjcli-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: yjcli
-Version: 0.1.4
+Version: 0.2.1
 Summary: Scaffold platforms, services, and AI agent wiring (Cursor/Claude/Codex) for YJ architecture repos.
 Project-URL: Homepage, https://github.com/yseiren87/yjcli
 Project-URL: Repository, https://github.com/yseiren87/yjcli
@@ -68,7 +68,7 @@ make backend NAME=api        # start one service
 
 Use with `-t` / `--type` (repeatable on `init` / `platform add`):
 
-`backend` · `backend-service` · `frontend` · `mobile-app` · `pc-app` · `cli` · `browser-extension`
+`backend` · `backend-service` · `frontend` · `mobile-app` · `pc-app` · `cli` · `browser-extension` · `scheduler`
 
 ## What `init` creates
 
@@ -76,14 +76,17 @@ Use with `-t` / `--type` (repeatable on `init` / `platform add`):
 - Skills under `.cursor/skills/`, `.claude/skills/`, `.agents/skills/` (Codex)
 - Claude `settings.json`
 - Root `Makefile`, `make.bat`, `TOOLS.md`, `.gitignore`
-- Selected platform roots (`*/scripts/run.sh` / `run.bat`)
+- `Diff.md` — user-maintained architecture difference and manual restoration notes
+- Selected platform roots with `scripts/run.*` and development/production deploy templates
 
-The root `Makefile` / `make.bat` is the repository-owned extension point for
-project automation. Projects may add commands such as `<platform>-build` or
-`<platform>-deploy` and reuse optional `NAME=<service>` selection. Defining and
-implementing init/install/build/deploy behavior is the project's responsibility;
-yjcli does not generate action scripts. Do not add per-service `scripts/`
-directories or per-service Makefiles.
+The root `Makefile` / `make.bat` wires platform run and deploy entry points. Deploy
+templates print the exact file to implement and fail until the project supplies
+its build/package and upload logic. They remain platform-level; do not add
+per-service `scripts/` directories or per-service Makefiles.
+
+`Diff.md` is created only when missing, including with `init --force`. yjcli never
+reads, updates, overwrites, or uses it for automatic restoration during sync or
+migration.
 
 Operating rules (skill routing, output discipline) are in `AGENTS.md` — not in
 `.cursor/rules` / `.claude/rules`.
@@ -102,6 +105,8 @@ inferring npm, uv, Go, or another language/runtime from project manifests.
 ```bash
 make <platform>                 # all services under that platform (concurrent)
 make <platform> NAME=<service>  # one service
+make <platform>-deploy-development [NAME=<service>]
+make <platform>-deploy-production [NAME=<service>]
 make help
 ```
 
@@ -111,7 +116,7 @@ make help
 |---------|------|
 | `yjcli sync agents` | After editing `AGENTS.md` — refreshes `CLAUDE.md` |
 | `yjcli sync skills` | Refresh packaged skills (Cursor / Claude / Codex) |
-| `yjcli sync make` | Overwrite root `Makefile` / `make.bat` and each installed platform’s `scripts/run.sh` · `run.bat` |
+| `yjcli sync make` | Overwrite root make/run files; install missing deploy scripts while preserving implemented ones |
 | `yjcli sync all` | Soft upgrade — mirror CLAUDE + skills + make (**keeps** your `AGENTS.md`) |
 | `yjcli sync migrate -y` | **Hard** upgrade — package template overwrites `AGENTS.md`, wipes skills dirs, drops legacy rules/`.agent`, refreshes settings/TOOLS/gitignore/make |
 
@@ -127,7 +132,7 @@ Edit `AGENTS.md` only; do not edit `CLAUDE.md` by hand. Use `migrate` when upgra
 
 ## Notes
 
-- `platform add` only creates platform roots (no services, no skills/Makefile — use `service add` / `sync`).
+- `platform add` creates platform roots and their run/deploy scripts (no services, skills, or root Makefile).
 - `service add` needs the platform root first (`init` or `platform add`).
 - Non-interactive: pass `-t` / `--all` / `-p` / `-n` as needed, and pass
   `--yes` for every `sync` command.
@@ -146,9 +151,11 @@ yjcli init --force
 yjcli platform add
 yjcli platform add --all
 yjcli platform add -t cli
+yjcli platform add -t scheduler
 
 yjcli service add
 yjcli service add -p backend -n api
+yjcli service add -p scheduler -n operations
 
 yjcli sync agents
 yjcli sync skills

{yjcli-0.1.4 → yjcli-0.2.1}/README.md

@@ -43,7 +43,7 @@ make backend NAME=api        # start one service
 
 Use with `-t` / `--type` (repeatable on `init` / `platform add`):
 
-`backend` · `backend-service` · `frontend` · `mobile-app` · `pc-app` · `cli` · `browser-extension`
+`backend` · `backend-service` · `frontend` · `mobile-app` · `pc-app` · `cli` · `browser-extension` · `scheduler`
 
 ## What `init` creates
 
@@ -51,14 +51,17 @@ Use with `-t` / `--type` (repeatable on `init` / `platform add`):
 - Skills under `.cursor/skills/`, `.claude/skills/`, `.agents/skills/` (Codex)
 - Claude `settings.json`
 - Root `Makefile`, `make.bat`, `TOOLS.md`, `.gitignore`
-- Selected platform roots (`*/scripts/run.sh` / `run.bat`)
+- `Diff.md` — user-maintained architecture difference and manual restoration notes
+- Selected platform roots with `scripts/run.*` and development/production deploy templates
 
-The root `Makefile` / `make.bat` is the repository-owned extension point for
-project automation. Projects may add commands such as `<platform>-build` or
-`<platform>-deploy` and reuse optional `NAME=<service>` selection. Defining and
-implementing init/install/build/deploy behavior is the project's responsibility;
-yjcli does not generate action scripts. Do not add per-service `scripts/`
-directories or per-service Makefiles.
+The root `Makefile` / `make.bat` wires platform run and deploy entry points. Deploy
+templates print the exact file to implement and fail until the project supplies
+its build/package and upload logic. They remain platform-level; do not add
+per-service `scripts/` directories or per-service Makefiles.
+
+`Diff.md` is created only when missing, including with `init --force`. yjcli never
+reads, updates, overwrites, or uses it for automatic restoration during sync or
+migration.
 
 Operating rules (skill routing, output discipline) are in `AGENTS.md` — not in
 `.cursor/rules` / `.claude/rules`.
@@ -77,6 +80,8 @@ inferring npm, uv, Go, or another language/runtime from project manifests.
 ```bash
 make <platform>                 # all services under that platform (concurrent)
 make <platform> NAME=<service>  # one service
+make <platform>-deploy-development [NAME=<service>]
+make <platform>-deploy-production [NAME=<service>]
 make help
 ```
 
@@ -86,7 +91,7 @@ make help
 |---------|------|
 | `yjcli sync agents` | After editing `AGENTS.md` — refreshes `CLAUDE.md` |
 | `yjcli sync skills` | Refresh packaged skills (Cursor / Claude / Codex) |
-| `yjcli sync make` | Overwrite root `Makefile` / `make.bat` and each installed platform’s `scripts/run.sh` · `run.bat` |
+| `yjcli sync make` | Overwrite root make/run files; install missing deploy scripts while preserving implemented ones |
 | `yjcli sync all` | Soft upgrade — mirror CLAUDE + skills + make (**keeps** your `AGENTS.md`) |
 | `yjcli sync migrate -y` | **Hard** upgrade — package template overwrites `AGENTS.md`, wipes skills dirs, drops legacy rules/`.agent`, refreshes settings/TOOLS/gitignore/make |
 
@@ -102,7 +107,7 @@ Edit `AGENTS.md` only; do not edit `CLAUDE.md` by hand. Use `migrate` when upgra
 
 ## Notes
 
-- `platform add` only creates platform roots (no services, no skills/Makefile — use `service add` / `sync`).
+- `platform add` creates platform roots and their run/deploy scripts (no services, skills, or root Makefile).
 - `service add` needs the platform root first (`init` or `platform add`).
 - Non-interactive: pass `-t` / `--all` / `-p` / `-n` as needed, and pass
   `--yes` for every `sync` command.
@@ -121,9 +126,11 @@ yjcli init --force
 yjcli platform add
 yjcli platform add --all
 yjcli platform add -t cli
+yjcli platform add -t scheduler
 
 yjcli service add
 yjcli service add -p backend -n api
+yjcli service add -p scheduler -n operations
 
 yjcli sync agents
 yjcli sync skills

{yjcli-0.1.4 → yjcli-0.2.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "yjcli"
-version = "0.1.4"
+version = "0.2.1"
 description = "Scaffold platforms, services, and AI agent wiring (Cursor/Claude/Codex) for YJ architecture repos."
 readme = "README.md"
 requires-python = ">=3.12"

{yjcli-0.1.4 → yjcli-0.2.1}/src/yjcli/data/skills/yj-arch-core/SKILL.md

@@ -30,11 +30,12 @@ mobile-app/           # yj-mobile-app
 pc-app/               # yj-pc-app
 cli/                  # yj-cli
 browser-extension/    # yj-browser-extension
+scheduler/            # yj-scheduler
 ```
 
 ```text
 {platform}/
-  scripts/            # platform-level only
+  scripts/            # platform run + deploy entry points
   {service_name}/     # one deployable / one app
 ```
 
@@ -45,10 +46,17 @@ browser-extension/    # yj-browser-extension
   `install`, or `help` targets. Do not add per-service `scripts/`.
   Root `make <platform>` starts all services under that platform (concurrent); `NAME=<service>` runs one.
   Platforms run via `*/scripts/run.*`; services are sibling dirs created with `yjcli service add`.
-- The root `Makefile` / `make.bat` is repository-owned and may be extended. Prefer
-  `<platform>-<action> [NAME=<service>]` when an action should target all services
-  or one service (for example, `backend-deploy`). The repository owns and implements
-  actions such as init/install/build/deploy; yjcli does not generate action scripts.
+- The root `Makefile` / `make.bat` wires platform run and deploy commands. Use
+  `<platform>-deploy-development|production [NAME=<service>]` for deploys.
+  `deploy-common.*` owns shared build/package preparation; the environment-specific
+  deploy script calls it and then owns upload/rollout. Generated deploy scripts fail
+  with an implementation prompt until the repository replaces their guarded stubs.
+- Deploy scripts are repository-owned after creation. `yjcli sync make` installs
+  missing deploy scripts but preserves existing ones.
+- `Diff.md` is an optional, user-maintained reference for meaningful architecture
+  differences from yjcli defaults and their manual restoration notes. Update it
+  when that record would help, but never treat it as an automated sync, migration,
+  backup, comparison, or restoration mechanism. Never place secrets in it.
 
 
 ## Environment (guardrails only)
@@ -64,7 +72,7 @@ Required files at each service root (no plain `.env`):
   `.env.local` convention unless a thin loader maps it to this structure.
 - Env field sets come from `templates/platform/envs/<kind>/` via platform mapping (`listen` / `worker` / `app`).
   - `listen`: `backend` (PORT 8080), `frontend` (PORT 5173)
-  - `worker`: `backend-service`, `browser-extension/native_*` (HOST/PORT optional)
+  - `worker`: `backend-service`, `browser-extension/native_*`, `scheduler` (HOST/PORT optional)
   - `app`: `cli`, `mobile-app`, `pc-app`, `browser-extension` (NAME/VERSION only)
   Do not invent fields outside those templates; environment filenames remain
   extensible through the `.env.<environment>` pattern above.
@@ -93,6 +101,7 @@ Required files at each service root (no plain `.env`):
 | `cli/**` | `yj-cli` |
 | `browser-extension/native_*/**` | `yj-backend-service` |
 | `browser-extension/**` (other) | `yj-browser-extension` |
+| `scheduler/**` | `yj-scheduler` |
 
 Never load all platform skills. Never apply a platform skill outside its folder.
 

yjcli-0.2.1/src/yjcli/data/skills/yj-scheduler/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: yj-scheduler
+description: >-
+  Long-running scheduler architecture for multiple periodic batch jobs. Use
+  only when editing scheduler/**. Language-agnostic: use an established
+  scheduling framework from the project's ecosystem without prescribing a
+  specific library. Covers job registration, execution isolation, overlap,
+  misfires, timezones, retries, locks, observability, and graceful shutdown.
+  Do not use for backend/, backend-service/, frontend/, mobile-app/, pc-app/,
+  cli/, or browser-extension/.
+---
+
+# yj-scheduler
+
+Requires `yj-arch-core`. Scope: **`scheduler/` only**.
+
+## Purpose
+
+Run multiple recurring batch jobs in one or more long-running scheduler
+processes. Use an established scheduling framework from the selected language
+ecosystem. Choose the concrete framework from the repository's stack and
+existing dependencies.
+
+Do not implement cron parsing, durable scheduling, misfire handling, or a
+`while` + `sleep` scheduling loop from scratch.
+
+## Shape
+
+```text
+scheduler/
+  scripts/                     # platform-level only
+  {scheduler_name}/            # one deployable scheduler process
+    apps/                      # entry: boot, registration, wiring, shutdown
+    services/
+      {job_name}/              # one batch workflow
+    domains/                   # optional: owned concepts only
+    modules/                   # scheduler adapter, db/api clients, lock, clock
+```
+
+- One scheduler process may register multiple related jobs.
+- Split jobs into separate `{scheduler_name}` deployables only when they need
+  independent deployment, scaling, dependencies, permissions, or failure isolation.
+- Do not add per-job `scripts/` or Makefiles. Root `make scheduler` runs all
+  scheduler services; `NAME=<scheduler_name>` runs one.
+- This is a long-running worker platform. `HOST` and `PORT` are optional and
+  should exist only when the process exposes a real endpoint.
+
+## Roles
+
+### entry (`apps`)
+
+- Create and configure the scheduling framework, register triggers, wire job
+  handlers, start the process, and perform graceful shutdown.
+- Keep registration declarative and discoverable in one entry area.
+- Framework callbacks must be thin: add execution context, call one flow, and
+  report its result. No query, transformation, or persistence logic in callbacks.
+
+### flow (`services/{job_name}`)
+
+- Each periodic job is an independently testable workflow.
+- Own job-specific input, orchestration, batching, checkpointing, and result shape.
+- A failure in one job must not terminate or block unrelated jobs.
+- Make operations idempotent whenever a retry or duplicate trigger is possible.
+
+### domain / infra
+
+- Add `domains/` only for concepts or shared policy owned by this process;
+  persistence is not required. Do not create a domain merely because a job exists.
+- Put framework integration, distributed locks, clocks, persistence, logging,
+  and external clients in `modules/`.
+- Do not import another platform's source tree; communicate through explicit
+  APIs or generated contracts.
+
+## Scheduling policy
+
+For every job, make these decisions explicit near its registration or config:
+
+- stable job identifier and handler
+- periodic or calendar trigger and explicit timezone
+- whether overlapping executions are allowed
+- misfire behavior (skip, coalesce, or catch up)
+- timeout, retry, and backoff behavior
+- concurrency limit and multi-instance ownership/locking strategy
+
+Never rely implicitly on the host's local timezone. Do not scatter schedule
+expressions across callbacks. Fixed business schedules may live in typed code or
+project configuration; expose them as environment-specific settings only when
+deployments genuinely need different schedules.
+
+When more than one scheduler instance can run, use the framework's persistent
+job store/single-run facility or a distributed lock. A process-local mutex does
+not prevent duplicate execution across instances.
+
+## Reliability and observability
+
+- Log job id, execution/run id, scheduled time, actual start, completion or
+  failure, duration, and retry attempt using structured fields.
+- Define shutdown behavior: stop accepting triggers, then finish or safely
+  cancel active jobs within a bounded grace period.
+- Long-running or high-volume jobs should use bounded batches and checkpoints so
+  they can resume safely after interruption.
+- Keep retry scope narrow. Do not retry permanent validation or authorization
+  failures as though they were transient infrastructure failures.
+- Inject or wrap the clock in flow/domain tests; do not make business rules
+  depend directly on wall-clock calls throughout the codebase.
+
+## Import direction
+
+```text
+entry/framework callback -> flow -> domain? -> infra
+entry -> infra
+flow  -> infra
+```
+
+Forbidden: business logic in trigger callbacks; flow importing entry/framework
+bootstrap; domain importing scheduler framework types; jobs calling one another
+for sequencing when a single coordinating flow owns the workflow.
+
+## Editing scope
+
+- Stay within `scheduler/{scheduler_name}/` unless the task explicitly changes
+  shared contracts or platform wiring.
+- Prefer extending an existing scheduler process for related jobs; do not create
+  one deployable per cron expression automatically.

{yjcli-0.1.4 → yjcli-0.2.1}/src/yjcli/data/templates/AGENTS.md

@@ -29,6 +29,7 @@ When creating, modifying, reviewing, or refactoring code:
 | `cli/**` | `yj-cli` |
 | `browser-extension/native_*/**` | `yj-backend-service` |
 | `browser-extension/**` (other) | `yj-browser-extension` |
+| `scheduler/**` | `yj-scheduler` |
 
 Never load all platform skills. Never apply a platform skill outside its folder.
 
@@ -57,8 +58,12 @@ Paths from `yjcli init` are fixed; add platform/app rows with `<path>` / `<role>
 | `AGENTS.md` | Agent / contributor guide (this file) — source of truth |
 | `CLAUDE.md` | Mirror of `AGENTS.md` — do not edit; refresh with `yjcli sync agents` |
 | `TOOLS.md` | Release-tools feature spec (version / deploy / git) |
-| `Makefile` | Extensible root entry — `make <platform>` (all services) or `NAME=<service>` (one); repository may add `<platform>-<action>` targets |
+| `Diff.md` | User-maintained reference for project differences from yjcli defaults; yjcli never updates or restores from it |
+| `Makefile` | Root entry — run via `make <platform>`; deploy via `<platform>-deploy-development\|production`, optionally with `NAME=<service>` |
 | `make.bat` | Extensible Windows counterpart of root Makefile |
+| `<platform>/scripts/deploy-common.*` | Repository-owned shared build/package implementation |
+| `<platform>/scripts/deploy-development.*` | Repository-owned development upload/deploy implementation |
+| `<platform>/scripts/deploy-production.*` | Repository-owned production upload/deploy implementation |
 | `.gitignore` | Canonical ignore rules |
 | `.cursor/skills/` | Cursor skills (copied from package) |
 | `.claude/skills/` | Claude skills (copied from package) |
@@ -93,6 +98,10 @@ Paths from `yjcli init` are fixed; add platform/app rows with `<path>` / `<role>
 
 # build
 <command>
+
+# deploy (generated stubs fail until implemented)
+make <platform>-deploy-development [NAME=<service>]
+make <platform>-deploy-production [NAME=<service>]
 ```
 
 ---
@@ -129,10 +138,13 @@ Paths from `yjcli init` are fixed; add platform/app rows with `<path>` / `<role>
 ### Do
 
 - `<item>`
+- Record meaningful architecture differences from yjcli defaults in `Diff.md` when useful for manual restoration.
 
 ### Don't
 
 - `<item>`
+- Do not expect `Diff.md` to drive sync, migration, comparison, backup, or automatic restoration.
+- Do not put secrets in `Diff.md`.
 
 ---
 
@@ -157,5 +169,6 @@ Paths from `yjcli init` are fixed; add platform/app rows with `<path>` / `<role>
 | Kind | Location |
 |------|----------|
 | Release tools spec | `TOOLS.md` |
+| Architecture differences | `Diff.md` |
 | Packaged skills (source) | installed via `yjcli` → `.cursor` / `.claude` / `.agents` skills |
 | `<kind>` | `<path>` |

yjcli-0.2.1/src/yjcli/data/templates/Diff.md

@@ -0,0 +1,9 @@
+# 아키텍처 차이점
+
+이 문서는 yjcli가 제공하는 기본 아키텍처와 현재 프로젝트 사이의 차이점을 기록하는 참고 자료다.
+
+템플릿이나 에이전트 연결 파일이 갱신된 뒤 프로젝트 고유의 변경 사항을 사용자가 직접 확인하고 복원할 때 활용한다.
+
+yjcli는 이 파일이 없을 때만 최초 생성하며, 이후에는 읽거나 수정하거나 덮어쓰지 않는다. 이 문서의 내용을 이용한 자동 비교, 백업 또는 복원도 수행하지 않는다.
+
+비밀번호, 토큰, 인증정보 등 시크릿은 기록하지 않는다.

yjcli-0.2.1/src/yjcli/data/templates/Makefile

@@ -0,0 +1,47 @@
+# Platform targets are discovered from */scripts/run.sh (after yjcli platform add).
+# Usage:
+#   make <platform>                 # all services under that platform (concurrent)
+#   make <platform> NAME=<service>  # one service
+# Deploy templates are platform-owned extension points. They intentionally fail
+# until the repository implements the printed build/package/upload steps.
+
+PLATFORMS := $(patsubst %/scripts/run.sh,%,$(wildcard */scripts/run.sh))
+DEPLOY_DEVELOPMENT_TARGETS := $(addsuffix -deploy-development,$(PLATFORMS))
+DEPLOY_PRODUCTION_TARGETS := $(addsuffix -deploy-production,$(PLATFORMS))
+
+.PHONY: help $(PLATFORMS) $(DEPLOY_DEVELOPMENT_TARGETS) $(DEPLOY_PRODUCTION_TARGETS)
+
+help:
+	@echo "Usage:"
+	@echo "  make <platform>                 # start all services concurrently"
+	@echo "  make <platform> NAME=<service>  # start one service"
+	@echo "  make <platform>-deploy-development [NAME=<service>]"
+	@echo "  make <platform>-deploy-production  [NAME=<service>]"
+	@echo ""
+	@echo "Available platforms (dirs with scripts/run.sh):"
+	@if [ -z "$(PLATFORMS)" ]; then \
+		echo "  (none — run: yjcli platform add)"; \
+	else \
+		for p in $(PLATFORMS); do echo "  $$p"; done; \
+	fi
+	@echo ""
+	@echo "Example: make backend"
+	@echo "         make backend NAME=api"
+	@echo "         make backend-deploy-development NAME=api"
+	@echo "         make backend-deploy-production NAME=api"
+
+$(PLATFORMS):
+	@test -x "$@/scripts/run.sh" || (echo "missing: $@/scripts/run.sh"; exit 1)
+	@if [ -n "$(NAME)" ]; then \
+		"$@/scripts/run.sh" "$(NAME)" $(ARGS); \
+	else \
+		"$@/scripts/run.sh" $(ARGS); \
+	fi
+
+$(DEPLOY_DEVELOPMENT_TARGETS): %-deploy-development:
+	@test -x "$*/scripts/deploy-development.sh" || (echo "missing: $*/scripts/deploy-development.sh"; exit 1)
+	@"$*/scripts/deploy-development.sh" "$(NAME)" $(ARGS)
+
+$(DEPLOY_PRODUCTION_TARGETS): %-deploy-production:
+	@test -x "$*/scripts/deploy-production.sh" || (echo "missing: $*/scripts/deploy-production.sh"; exit 1)
+	@"$*/scripts/deploy-production.sh" "$(NAME)" $(ARGS)

{yjcli-0.1.4 → yjcli-0.2.1}/src/yjcli/data/templates/make.bat

@@ -1,12 +1,24 @@
 @echo off
 setlocal EnableExtensions EnableDelayedExpansion
-rem Extend this root file with repository-owned platform-action commands as needed,
-rem for example: make.bat backend-deploy NAME=api. yjcli does not define them.
+rem Deploy scripts intentionally fail until their printed implementation steps are completed.
 
 if /I "%~1"=="" goto help
 if /I "%~1"=="help" goto help
 
-set "PLATFORM=%~1"
+set "TARGET=%~1"
+set "PLATFORM=%TARGET:-deploy-development=%"
+if /I not "%PLATFORM%"=="%TARGET%" (
+  set "DEPLOY_ENV=development"
+  goto parse_start
+)
+set "PLATFORM=%TARGET:-deploy-production=%"
+if /I not "%PLATFORM%"=="%TARGET%" (
+  set "DEPLOY_ENV=production"
+  goto parse_start
+)
+set "PLATFORM=%TARGET%"
+
+:parse_start
 if not exist "%PLATFORM%\scripts\run.bat" (
   echo Unknown target: %PLATFORM%
   echo Expected: %PLATFORM%\scripts\run.bat ^(yjcli platform add^)
@@ -23,6 +35,10 @@ shift
 goto parse
 
 :run_exec
+if defined DEPLOY_ENV (
+  call "%PLATFORM%\scripts\deploy-%DEPLOY_ENV%.bat" "%NAME%"
+  exit /b !ERRORLEVEL!
+)
 if "%NAME%"=="" (
   call "%PLATFORM%\scripts\run.bat"
 ) else (
@@ -34,6 +50,8 @@ exit /b %ERRORLEVEL%
 echo Usage:
 echo   make.bat ^<platform^>                 # all services ^(separate windows^)
 echo   make.bat ^<platform^> NAME=^<service^>  # one service
+echo   make.bat ^<platform^>-deploy-development [NAME=^<service^>]
+echo   make.bat ^<platform^>-deploy-production  [NAME=^<service^>]
 echo.
 echo Available platforms (dirs with scripts\run.bat):
 set "FOUND="
@@ -47,4 +65,6 @@ if not defined FOUND echo   ^(none — run: yjcli platform add^)
 echo.
 echo Example: make.bat backend
 echo          make.bat backend NAME=api
+echo          make.bat backend-deploy-development NAME=api
+echo          make.bat backend-deploy-production NAME=api
 exit /b 0

yjcli-0.2.1/src/yjcli/data/templates/platform/scripts/deploy-common.bat

@@ -0,0 +1,33 @@
+@echo off
+setlocal EnableExtensions
+rem Shared build/package preparation for development and production deploys.
+rem Replace the implementation guard below with repository-specific commands.
+
+set "SCRIPT_DIR=%~dp0"
+for %%D in ("%SCRIPT_DIR%..") do set "PLATFORM_DIR=%%~fD"
+set "ENVIRONMENT=%~1"
+set "NAME=%~2"
+
+if /I not "%ENVIRONMENT%"=="development" if /I not "%ENVIRONMENT%"=="production" (
+  echo usage: %~nx0 ^<development^|production^> [service] [args...]
+  exit /b 1
+)
+
+if defined NAME if not exist "%PLATFORM_DIR%\%NAME%\" (
+  echo unknown service: %NAME% ^(expected %PLATFORM_DIR%\%NAME%^)
+  exit /b 1
+)
+
+for %%D in ("%PLATFORM_DIR%") do set "PLATFORM_NAME=%%~nxD"
+echo [deploy] platform: %PLATFORM_NAME%
+echo [deploy] environment: %ENVIRONMENT%
+if defined NAME (echo [deploy] service: %NAME%) else echo [deploy] service: all
+echo deploy common is not implemented.
+echo Implement build/package logic in: %SCRIPT_DIR%deploy-common.bat
+echo Examples: docker build, archive creation, frontend build
+
+rem Implementation examples:
+rem docker build -t "example/%NAME%:%ENVIRONMENT%" "%PLATFORM_DIR%"
+rem tar -a -c -f "%NAME%.zip" -C "%PLATFORM_DIR%" "%NAME%"
+rem cd /d "%PLATFORM_DIR%\%NAME%" ^&^& npm ci ^&^& npm run build
+exit /b 1

yjcli-0.2.1/src/yjcli/data/templates/platform/scripts/deploy-common.sh

@@ -0,0 +1,35 @@
+#!/usr/bin/env bash
+# Shared build/package preparation for development and production deploys.
+# Replace the implementation guard below with repository-specific commands.
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+PLATFORM_DIR="$(cd "$SCRIPT_DIR/.." && pwd)"
+ENVIRONMENT="${1:-}"
+NAME="${2:-}"
+
+case "$ENVIRONMENT" in
+  development|production) ;;
+  *)
+    echo "usage: $0 <development|production> [service] [args...]"
+    exit 1
+    ;;
+esac
+
+if [ -n "$NAME" ] && [ ! -d "$PLATFORM_DIR/$NAME" ]; then
+  echo "unknown service: $NAME (expected $PLATFORM_DIR/$NAME)"
+  exit 1
+fi
+
+echo "[deploy] platform: $(basename "$PLATFORM_DIR")"
+echo "[deploy] environment: $ENVIRONMENT"
+echo "[deploy] service: ${NAME:-all}"
+echo "deploy common is not implemented."
+echo "Implement build/package logic in: $SCRIPT_DIR/deploy-common.sh"
+echo "Examples: docker build, archive creation, frontend build"
+
+# Implementation examples:
+# docker build -t "example/${NAME:-platform}:$ENVIRONMENT" "$PLATFORM_DIR"
+# tar -czf "${NAME:-platform}.tar.gz" -C "$PLATFORM_DIR" "${NAME:-.}"
+# (cd "$PLATFORM_DIR/$NAME" && npm ci && npm run build)
+exit 1

yjcli-0.2.1/src/yjcli/data/templates/platform/scripts/deploy-development.bat

@@ -0,0 +1,21 @@
+@echo off
+setlocal EnableExtensions
+rem Development deployment entry point. Keep shared preparation in deploy-common.bat.
+
+set "SCRIPT_DIR=%~dp0"
+set "NAME=%~1"
+shift
+
+call "%SCRIPT_DIR%deploy-common.bat" development "%NAME%" %*
+if errorlevel 1 exit /b %ERRORLEVEL%
+
+echo development upload is not implemented.
+echo Implement upload/deploy logic in: %SCRIPT_DIR%deploy-development.bat
+echo Examples: docker push, scp, S3 upload, kubectl apply
+
+rem Development upload examples:
+rem docker push "registry.example.com/%NAME%:development"
+rem scp "%ARTIFACT%" "dev-server:/srv/%NAME%/"
+rem aws s3 sync "%DIST_DIR%" "s3://example-development/%NAME%/"
+rem kubectl apply -k deploy/overlays/development
+exit /b 1

yjcli-0.2.1/src/yjcli/data/templates/platform/scripts/deploy-development.sh

@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+# Development deployment entry point. Keep shared preparation in deploy-common.sh.
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+NAME="${1:-}"
+shift || true
+
+"$SCRIPT_DIR/deploy-common.sh" development "$NAME" "$@"
+
+echo "development upload is not implemented."
+echo "Implement upload/deploy logic in: $SCRIPT_DIR/deploy-development.sh"
+echo "Examples: docker push, scp, S3 upload, kubectl apply"
+
+# Development upload examples:
+# docker push "registry.example.com/$NAME:development"
+# scp "$ARTIFACT" "dev-server:/srv/$NAME/"
+# aws s3 sync "$DIST_DIR" "s3://example-development/$NAME/"
+# kubectl apply -k deploy/overlays/development
+exit 1

yjcli-0.2.1/src/yjcli/data/templates/platform/scripts/deploy-production.bat

@@ -0,0 +1,21 @@
+@echo off
+setlocal EnableExtensions
+rem Production deployment entry point. Keep shared preparation in deploy-common.bat.
+
+set "SCRIPT_DIR=%~dp0"
+set "NAME=%~1"
+shift
+
+call "%SCRIPT_DIR%deploy-common.bat" production "%NAME%" %*
+if errorlevel 1 exit /b %ERRORLEVEL%
+
+echo production upload is not implemented.
+echo Implement upload/deploy logic in: %SCRIPT_DIR%deploy-production.bat
+echo Examples: registry push, production upload, release rollout
+
+rem Recommended production steps:
+rem - validate VERSION or release tag
+rem - upload the artifact or push the container image
+rem - deploy to production and run a health check
+rem - roll back on failure
+exit /b 1

yjcli-0.2.1/src/yjcli/data/templates/platform/scripts/deploy-production.sh

@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+# Production deployment entry point. Keep shared preparation in deploy-common.sh.
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+NAME="${1:-}"
+shift || true
+
+"$SCRIPT_DIR/deploy-common.sh" production "$NAME" "$@"
+
+echo "production upload is not implemented."
+echo "Implement upload/deploy logic in: $SCRIPT_DIR/deploy-production.sh"
+echo "Examples: registry push, production upload, release rollout"
+
+# Recommended production steps:
+# - validate VERSION or release tag
+# - upload the artifact or push the container image
+# - deploy to the production environment and run a health check
+# - roll back on failure
+exit 1

{yjcli-0.1.4 → yjcli-0.2.1}/src/yjcli/modules/constants.py

@@ -10,6 +10,7 @@ PLATFORMS: tuple[str, ...] = (
     "pc-app",
     "cli",
     "browser-extension",
+    "scheduler",
 )
 
 RESERVED_SERVICE_NAMES: frozenset[str] = frozenset({"scripts", "proto"})
@@ -26,4 +27,5 @@ PLATFORM_ENV: dict[str, tuple[str, dict[str, str]]] = {
     "mobile-app": ("app", {}),
     "pc-app": ("app", {}),
     "browser-extension": ("app", {}),
+    "scheduler": ("worker", {}),
 }

{yjcli-0.1.4 → yjcli-0.2.1}/src/yjcli/services/scaffold.py

@@ -28,6 +28,17 @@ _DEFAULT_ENV_FILE_NAMES = (
     ".env.examples",
 )
 
+_PLATFORM_SCRIPT_NAMES = (
+    "run.sh",
+    "run.bat",
+    "deploy-common.sh",
+    "deploy-common.bat",
+    "deploy-development.sh",
+    "deploy-development.bat",
+    "deploy-production.sh",
+    "deploy-production.bat",
+)
+
 
 def existing_platforms(root: Path) -> list[str]:
     return [p for p in PLATFORMS if (root / p).is_dir()]
@@ -43,14 +54,21 @@ def create_platform(root: Path, platform: str) -> None:
     scripts_dir.mkdir(parents=True, exist_ok=True)
 
     templates = paths.templates_dir()
-    run_sh = templates / "platform" / "scripts" / "run.sh"
-    run_bat = templates / "platform" / "scripts" / "run.bat"
-    if not run_sh.is_file() or not run_bat.is_file():
-        abort(f"missing platform scripts under {templates / 'platform' / 'scripts'}")
-
-    shutil.copy2(run_sh, scripts_dir / "run.sh")
-    shutil.copy2(run_bat, scripts_dir / "run.bat")
-    (scripts_dir / "run.sh").chmod((scripts_dir / "run.sh").stat().st_mode | 0o111)
+    script_templates = templates / "platform" / "scripts"
+    missing = [
+        name
+        for name in _PLATFORM_SCRIPT_NAMES
+        if not (script_templates / name).is_file()
+    ]
+    if missing:
+        abort(f"missing platform scripts under {script_templates}: {', '.join(missing)}")
+
+    for name in _PLATFORM_SCRIPT_NAMES:
+        source = script_templates / name
+        target = scripts_dir / name
+        shutil.copy2(source, target)
+        if name.endswith(".sh"):
+            target.chmod(target.stat().st_mode | 0o111)
 
     if platform == "backend":
         proto = dest / "proto"
@@ -122,7 +140,7 @@ def create_service(root: Path, platform: str, name: str) -> None:
     _copy_env_templates(platform, name, base)
     _copy_platform_extras(platform, name, base)
 
-    if platform in {"backend", "backend-service"}:
+    if platform in {"backend", "backend-service", "scheduler"}:
         for sub in ("apps", "services", "domains", "modules"):
             (base / sub).mkdir(exist_ok=True)
     elif platform == "frontend":
@@ -242,3 +260,5 @@ def add_service_flow(
     typer.echo(f"run all: make {chosen}")
     typer.echo(f"run one: make {chosen} NAME={name}")
     typer.echo(f"  or: {chosen}/scripts/run.sh [{name}]")
+    typer.echo(f"deploy development: make {chosen}-deploy-development NAME={name}")
+    typer.echo(f"deploy production: make {chosen}-deploy-production NAME={name}")

{yjcli-0.1.4 → yjcli-0.2.1}/src/yjcli/services/sync.py

@@ -76,7 +76,7 @@ def sync_skills(root: Path, *, force: bool = True) -> None:
 
 
 def sync_make(root: Path, *, force: bool = True) -> None:
-    """Overwrite root Makefile/make.bat and each installed platform's run scripts."""
+    """Refresh managed make/run files and install missing deploy templates."""
     templates = paths.templates_dir()
     for name in ("Makefile", "make.bat"):
         src = templates / name
@@ -85,10 +85,23 @@ def sync_make(root: Path, *, force: bool = True) -> None:
         copy_file(src, root / name, force=force)
     typer.echo("synced: packaged Makefile, make.bat -> repo root")
 
-    run_sh = templates / "platform" / "scripts" / "run.sh"
-    run_bat = templates / "platform" / "scripts" / "run.bat"
-    if not run_sh.is_file() or not run_bat.is_file():
-        abort(f"missing packaged platform scripts under {run_sh.parent}")
+    scripts_src = templates / "platform" / "scripts"
+    managed_names = ("run.sh", "run.bat")
+    deploy_names = (
+        "deploy-common.sh",
+        "deploy-common.bat",
+        "deploy-development.sh",
+        "deploy-development.bat",
+        "deploy-production.sh",
+        "deploy-production.bat",
+    )
+    missing = [
+        name
+        for name in (*managed_names, *deploy_names)
+        if not (scripts_src / name).is_file()
+    ]
+    if missing:
+        abort(f"missing packaged platform scripts under {scripts_src}: {', '.join(missing)}")
 
     installed = [p for p in PLATFORMS if (root / p).is_dir()]
     if not installed:
@@ -98,13 +111,21 @@ def sync_make(root: Path, *, force: bool = True) -> None:
     for platform in installed:
         scripts_dir = root / platform / "scripts"
         ensure_real_dir(scripts_dir)
-        dest_sh = scripts_dir / "run.sh"
-        dest_bat = scripts_dir / "run.bat"
-        copy_file(run_sh, dest_sh, force=force)
-        copy_file(run_bat, dest_bat, force=force)
-        if dest_sh.is_file():
-            dest_sh.chmod(dest_sh.stat().st_mode | 0o111)
-        typer.echo(f"synced: {platform}/scripts/run.sh, run.bat")
+        for name in managed_names:
+            copy_file(scripts_src / name, scripts_dir / name, force=force)
+        for name in deploy_names:
+            copy_file(scripts_src / name, scripts_dir / name, skip_existing=True)
+        executable_names = (
+            "run.sh",
+            "deploy-common.sh",
+            "deploy-development.sh",
+            "deploy-production.sh",
+        )
+        for name in executable_names:
+            target = scripts_dir / name
+            if target.is_file():
+                target.chmod(target.stat().st_mode | 0o111)
+        typer.echo(f"synced: {platform}/scripts (run refreshed; deploy preserved)")
 
 
 def sync_all(root: Path, *, force: bool = True) -> None:

{yjcli-0.1.4 → yjcli-0.2.1}/src/yjcli/services/wiring.py

@@ -31,7 +31,7 @@ def ensure_agent_wiring(root: Path, *, force: bool = False) -> None:
 
 
 def ensure_root_from_templates(root: Path, *, force: bool = False) -> None:
-    """Copy root Makefile / TOOLS.md / .gitignore / make.bat from packaged templates."""
+    """Copy managed root templates and create the user-owned Diff.md once."""
     templates = paths.templates_dir()
     for name in (".gitignore", "Makefile", "make.bat", "TOOLS.md"):
         src = templates / name
@@ -39,3 +39,9 @@ def ensure_root_from_templates(root: Path, *, force: bool = False) -> None:
             typer.echo(f"warn: missing template: {src}", err=True)
             continue
         copy_file(src, root / name, force=force)
+
+    diff_src = templates / "Diff.md"
+    if not diff_src.is_file():
+        typer.echo(f"warn: missing template: {diff_src}", err=True)
+    else:
+        copy_file(diff_src, root / "Diff.md", skip_existing=True)

yjcli-0.1.4/src/yjcli/data/templates/Makefile

@@ -1,34 +0,0 @@
-# Platform targets are discovered from */scripts/run.sh (after yjcli platform add).
-# Usage:
-#   make <platform>                 # all services under that platform (concurrent)
-#   make <platform> NAME=<service>  # one service
-# Extend this root file for repository-owned work when needed. A useful pattern
-# is <platform>-<action> with the same optional NAME selector, for example
-# `make backend-deploy [NAME=api]`. yjcli does not define those actions.
-
-PLATFORMS := $(patsubst %/scripts/run.sh,%,$(wildcard */scripts/run.sh))
-
-.PHONY: help $(PLATFORMS)
-
-help:
-	@echo "Usage:"
-	@echo "  make <platform>                 # start all services concurrently"
-	@echo "  make <platform> NAME=<service>  # start one service"
-	@echo ""
-	@echo "Available platforms (dirs with scripts/run.sh):"
-	@if [ -z "$(PLATFORMS)" ]; then \
-		echo "  (none — run: yjcli platform add)"; \
-	else \
-		for p in $(PLATFORMS); do echo "  $$p"; done; \
-	fi
-	@echo ""
-	@echo "Example: make backend"
-	@echo "         make backend NAME=api"
-
-$(PLATFORMS):
-	@test -x "$@/scripts/run.sh" || (echo "missing: $@/scripts/run.sh"; exit 1)
-	@if [ -n "$(NAME)" ]; then \
-		"$@/scripts/run.sh" "$(NAME)" $(ARGS); \
-	else \
-		"$@/scripts/run.sh" $(ARGS); \
-	fi