feat(flow): enforce numeric releases and deploy routing

Author: rldyourmnd

.github/workflows/release.yml

@@ -4,7 +4,6 @@ on:
   push:
     tags:
       - "[0-9]*.[0-9]*.[0-9]*"
-      - "[0-9]*.[0-9]*.[0-9]*-*"
   workflow_dispatch:
     inputs:
       version:
@@ -60,8 +59,8 @@ jobs:
             echo "release version is empty; tag push or workflow_dispatch input required" >&2
             exit 1
           fi
-          if ! printf '%s' "$version" | grep -Eq '^[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.-]+)?$'; then
-            echo "release version '$version' is not SemVer X.Y.Z[-pre]" >&2
+          if ! printf '%s' "$version" | grep -Eq '^[0-9]+\.[0-9]+\.[0-9]+$'; then
+            echo "release version '$version' is not numeric SemVer X.Y.Z" >&2
             exit 1
           fi
           file_version="$(tr -d '[:space:]' < VERSION)"

CHANGELOG.md

@@ -6,6 +6,19 @@ The format follows Keep a Changelog, and marketplace/plugin versions follow Sema
 
 ## [Unreleased]
 
+## [0.4.9] - 2026-05-22
+
+### Changed
+
+- Product release tags remain numeric-only (`X.Y.Z`) and the release workflow
+  now rejects prerelease tag forms for this owner-standard configuration pack.
+- `rldyour-flow` `ry-start` now routes explicit deploy/server rollout intent
+  into `ry-deploy` after implementation validation and sync.
+- `rldyour-flow` `ry-review` now defines time-window, PR, issue, branch, and
+  last-deploy target parsing before reviewer dispatch.
+- `rldyour-flow` `ry-newp` now explicitly seeds `CONTEXT-01-CORE.md` and
+  `FUTURE-01-VISION.md` after approved scaffold commits.
+
 ## [0.4.8] - 2026-05-22
 
 ### Changed

VERSION

@@ -1 +1 @@
-0.4.8
+0.4.9

plugins/rldyour-flow/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rldyour-flow",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "description": "Autonomous Russian-first SDLC workflow for Codex: deep ry-init context packs, instruction docs sync, fullrepo sync, ry-repair, reviewer skills, deploy, and non-blocking hooks. RU: автономный SDLC-слой Codex для инициализации, реализации, ревью, ремонта репозитория, деплоя и синхронизации.",
   "author": {
     "name": "Danil Silantyev (github:rldyourmnd), CEO NDDev",

plugins/rldyour-flow/skills/ry-newp/SKILL.md

@@ -18,6 +18,14 @@ Design a new project with enough rigor that implementation can start with clear
 5. Ask for approval before creating any scaffold code.
 6. If scaffold is approved, create the minimal useful project structure, commit atomically, and initialize Serena memories.
 
+## Serena Memory Seeds
+
+After scaffold approval and the first real commit, initialize Serena memories
+from verified project facts only. At minimum seed `CONTEXT-01-CORE.md` for
+current source-of-truth facts and `FUTURE-01-VISION.md` for future-shape
+constraints. Propose ADR memories for non-obvious decisions, but do not write
+ADR meaning without explicit owner approval.
+
 ## Output
 
 Produce English project documents and Russian user-facing summaries.

plugins/rldyour-flow/skills/ry-review/SKILL.md

@@ -19,6 +19,22 @@ Find real issues before merge or deploy. Default mode is report-only: do not edi
 6. Consolidate findings by severity and confidence. Validate uncertain findings with code evidence.
 7. Output Russian report with exact paths, impact, suggested fixes, and whether each finding is must-fix.
 
+## Review Target Parsing
+
+When the owner asks for a time-window or history-based review, resolve the
+review target before dispatching reviewers:
+
+- `last N days` / `за последние N дней`: compute the exact commit range with
+  `git log --since`.
+- `since DATE` / `с DATE`: use the explicit date as the lower bound.
+- `PR #N` or `issue #N`: inspect the GitHub PR/issue and verify its relevance
+  against current code before treating it as a finding.
+- `branch vs main`: review the merge-base diff plus related commits.
+- `since last deploy`: identify the last verified deployment marker or ask for
+  it if the repository has no durable deploy record.
+
+Report the resolved commit range, PR/issue IDs, and any unresolved evidence gap.
+
 ## Reviewer Tracks
 
 Read `references/reviewer-protocol.md`. These tracks are orchestrated by `ry-review` or `ry-start`; they are not broad implicit-entry skills.

plugins/rldyour-flow/skills/ry-start/SKILL.md

@@ -27,6 +27,16 @@ Implement a task to a high-quality, scalable, synchronized state. Speed is secon
 14. Run review phase with subagents for architecture, quality, consistency, integration, verification, and security when applicable.
 15. Run `flow-post-task-sync` before final response.
 
+## Deploy Intent Routing
+
+If the owner request includes deploy, production, server rollout,
+sync-and-deploy, or a named deployment target, do not finish after
+implementation. After code validation, reviewer fixes, and Serena/docs sync,
+route into `ry-deploy` with the same scope and target. If the deploy contract
+is incomplete, ask for the missing server, branch, environment, health-check,
+rollback, or credential decision before deploying. Never invent server access
+or deployment targets.
+
 ## Automatic Helper Routing
 
 The owner normally invokes only `rldyour-flow` commands and writes prompts in Russian. `ry-start` must route helper skills automatically instead of waiting for explicit helper skill names:

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rldyour-codex"
-version = "0.4.8"
+version = "0.4.9"
 description = "Personal Codex marketplace with rldyour plugins, MCP servers, skills, hooks, and SDLC tooling."
 readme = "README.md"
 requires-python = ">=3.13,<3.14"