yjcli 0.1.4__tar.gz → 0.2.0__tar.gz

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: yjcli
-Version: 0.1.4
+Version: 0.2.0
 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
 
@@ -146,9 +146,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.0}/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
 
@@ -121,9 +121,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.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "yjcli"
-version = "0.1.4"
+version = "0.2.0"
 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.0}/src/yjcli/data/skills/yj-arch-core/SKILL.md

@@ -30,6 +30,7 @@ mobile-app/           # yj-mobile-app
 pc-app/               # yj-pc-app
 cli/                  # yj-cli
 browser-extension/    # yj-browser-extension
+scheduler/            # yj-scheduler
 ```
 
 ```text
@@ -64,7 +65,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 +94,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.0/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.0}/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.
 

{yjcli-0.1.4 → yjcli-0.2.0}/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.0}/src/yjcli/services/scaffold.py

@@ -122,7 +122,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":