projectops 4.89.3 → 4.90.2

package/README.md

@@ -8,13 +8,6 @@
 
 [![npm](https://img.shields.io/npm/v/projectops?label=npm)](https://www.npmjs.com/package/projectops) [![Release](https://img.shields.io/github/v/release/Cassiiopeia/projectops?label=release)](https://github.com/Cassiiopeia/projectops/releases) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![Docs](https://img.shields.io/badge/docs-site-4f46e5)](https://cassiiopeia.github.io/projectops/)
 
-**Status: actively maintained.** npm `latest` is exactly what is on the `main` branch; work in progress on `develop` is never published. Versions can still ship several times a day. Note that `npx projectops@<version>` pins the installer only (workflow templates always come from the current `main`) ([releases](https://github.com/Cassiiopeia/projectops/releases)).
-
-<!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->
-## Latest version : v4.89.3 (2026-11-07)
-
-[View full version history](CHANGELOG.md)
-
 </div>
 
 ---
@@ -34,6 +27,13 @@
 
 > This is a **real run** on a sample Spring project (the wizard follows your system language, or use `--lang en|ko`). Version numbers shown were current when it was recorded. For non-interactive use and every option, see the [CLI reference](https://cassiiopeia.github.io/projectops/cli).
 
+**Status: actively maintained.** npm `latest` is exactly what is on the `main` branch; work in progress on `develop` is never published. Versions can still ship several times a day. Note that `npx projectops@<version>` pins the installer only (workflow templates always come from the current `main`) ([releases](https://github.com/Cassiiopeia/projectops/releases)).
+
+<!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->
+## Latest version : v4.90.2 (2026-11-08)
+
+[View full version history](CHANGELOG.md)
+
 ---
 
 ## Why this template?
@@ -107,6 +107,14 @@ Open a PR from the development branch to `main` and it writes the release notes,
 **Drive it from your agent:** `/pro-changelog-deploy` pushes develop and opens the release PR for you.
 
 
+### 4. See UI mockups, press through them, and pick one
+
+![Two linked mockup screens updating each other](https://raw.githubusercontent.com/Cassiiopeia/projectops/main/docs/images/feature-ui-design.gif)
+
+Ask for mockups and get a local page where they really move and respond. Here two screens share one state: an order placed on the left appears in the kitchen on the right. Mockups use your repo's tokens and fonts, and the same run can post a GIF like this one to the issue.
+
+**Drive it from your agent:** `/pro-ui-design` shows the options, records your pick for the next skills, and hands it to a designer if you cannot decide.
+
 ---
 
 ## Make it yours

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projectops",
-  "version": "4.89.3",
+  "version": "4.90.2",
   "description": "One npx install for GitHub release automation: semantic versioning, changelogs, release PRs, CI/CD workflows and AI agent skills",
   "keywords": [
     "github-actions",

package/src/core/migrations/index.js

@@ -50,6 +50,16 @@ export function applySafeMigrations(targetRoot, entries) {
 //   log      - 한 줄 출력 함수 (기본 console.log)
 //   removeLegacy - true면 confirm 티어(구세대 배포 워크플로우)도 .bak 무해화 (--remove-legacy, #809)
 // 반환: { applied: [결과], confirmPending: [entry], askPending: [entry] }
+// 폐기 워크플로에서 옮긴 설정 > 화면과 실행 기록용 줄 (사용자가 설정이 옮겨졌는지 확인, #1060)
+export function describeCarriedSettings(results) {
+  const lines = [];
+  for (const result of results) {
+    if (result.carried?.length) lines.push(t("migrate.safe.carried", { file: result.from, keys: result.carried.join(", ") }));
+    if (result.carryFailed) lines.push(t("migrate.safe.carryFailed", { file: result.from, error: result.carryFailed }));
+  }
+  return lines;
+}
+
 export async function runMigrations({ targetRoot = ".", askYesNo = null, log = console.log, removeLegacy = false } = {}) {
   const { safe, confirm, ask } = detectMigrations(targetRoot);
   if (safe.length === 0 && confirm.length === 0 && ask.length === 0) {
@@ -73,6 +83,7 @@ export async function runMigrations({ targetRoot = ".", askYesNo = null, log = c
       const failed = applied.filter((r) => r.action === "error");
       log(t("migrate.safe.done", { n: ok.length, failed: failed.length ? t("migrate.safe.failed", { n: failed.length }) : "" }));
       for (const f of failed) log(`   ⚠️ ${f.from}: ${f.error}`);
+      for (const line of describeCarriedSettings(ok)) log(line);
     } else {
       log(t("migrate.safe.skip"));
     }

package/src/core/migrations/rules/obsolete-workflows.js

@@ -23,9 +23,10 @@ export function detect(targetRoot, entry) {
 export function apply(targetRoot, entry) {
   // 무해화 전 설정 이관 (실패해도 무해화는 진행 — 부분 실패 허용 원칙)
   let carried = [];
+  let carryFailed = null;
   if (entry.settingsExtractor && EXTRACTORS[entry.settingsExtractor]) {
     try { carried = EXTRACTORS[entry.settingsExtractor](targetRoot, entry).carried; }
-    catch { carried = []; }
+    catch (error) { carried = []; carryFailed = error?.message || String(error); }
   }
   const src = target(targetRoot, entry);
   const bak = `${src}.bak`;
@@ -33,5 +34,6 @@ export function apply(targetRoot, entry) {
   renameSync(src, bak);
   const result = { action: "bak", from: entry.file, to: `${entry.file}.bak` };
   if (carried.length > 0) result.carried = carried;
+  if (carryFailed) result.carryFailed = carryFailed;
   return result;
 }

package/src/i18n/migrate.en.js

@@ -48,6 +48,8 @@ export default {
   "migrate.safe.ask": "Clean up the {n} file(s) above? (workflows are neutralized as .bak and can be restored)",
   "migrate.safe.done": "Legacy cleanup done: {n}{failed}",
   "migrate.safe.failed": " ({n} failed)",
+  "migrate.safe.carried": "   Settings moved to version.yml from {file}: {keys}",
+  "migrate.safe.carryFailed": "   ⚠️ Could not move settings from {file}: {error}. Copy them to version.yml by hand; the old file is kept as .bak",
   "migrate.safe.skip": "Skipping legacy cleanup (you will be asked again on the next update)",
   "migrate.dir.found": "Found {n} output folder(s) with an old name. They contain your documents, so they are moved only after confirmation:",
   "migrate.dir.ask": "Move the folders above to the new name? (no files are lost, the original is kept on conflict)",

package/src/i18n/migrate.ko.js

@@ -48,6 +48,8 @@ export default {
   "migrate.safe.ask": "위 {n}개를 정리할까요? (워크플로우는 .bak 무해화 — 복원 가능)",
   "migrate.safe.done": "✅ 레거시 정리 완료: {n}개{failed}",
   "migrate.safe.failed": " (실패 {n}개)",
+  "migrate.safe.carried": "   {file}의 설정을 version.yml로 옮겼습니다: {keys}",
+  "migrate.safe.carryFailed": "   ⚠️ {file}의 설정을 옮기지 못했습니다: {error}. version.yml에 직접 옮겨 주세요. 옛 파일은 .bak으로 남아 있습니다",
   "migrate.safe.skip": "→ 레거시 정리를 건너뜁니다 (다음 업데이트 때 다시 안내)",
   "migrate.dir.found": "📁 구명칭 산출물 폴더 {n}개 감지 — 사용자 문서가 들어 있어 확인 후 이동합니다:",
   "migrate.dir.ask": "위 폴더를 새 이름으로 이동할까요? (파일 손실 없음 — 충돌 시 원본 유지)",