@mediadatafusion/pi-workflow-suite 0.0.11 → 0.0.13

package/scripts/prepare-package-readme.mjs

@@ -2,26 +2,21 @@
 import { existsSync, readFileSync, renameSync, unlinkSync, writeFileSync } from 'node:fs';
 import { dirname, resolve } from 'node:path';
 import { fileURLToPath } from 'node:url';
+import { packageMediaUrl, packageMediaUrls } from './package-media-config.mjs';
 
 const scriptDir = dirname(fileURLToPath(import.meta.url));
 const repoRoot = resolve(scriptDir, '..');
 const readmePath = resolve(repoRoot, 'README.md');
 const backupPath = resolve(repoRoot, '.package-readme.source.md');
 const publishMarkerPath = resolve(repoRoot, '.package-readme.publish');
-const mediaVersion = '0.0.6';
-
-function mediaCdn(assetPath) {
-  return `https://cdn.jsdelivr.net/npm/@mediadatafusion/pi-workflow-suite@${mediaVersion}/${assetPath}`;
-}
-
 function buildPackageReadme(sourceReadme) {
   const headerBlock = `# Pi Workflow Suite\n\n${
-    `![Pi Workflow Suite — structured workflow orchestration for Pi](${mediaCdn('docs/assets/pi-workflow-suite-header.png')})`
+    `![Pi Workflow Suite — structured workflow orchestration for Pi](${packageMediaUrls.header})`
   }\n\n${[
-    `[![Install](${mediaCdn('docs/assets/readme-link-install.svg')})](#installation)`,
-    `[![Quick Start](${mediaCdn('docs/assets/readme-link-quick-start.svg')})](#quick-start)`,
-    `[![Commands](${mediaCdn('docs/assets/readme-link-commands.svg')})](#core-commands)`,
-    `[![Settings](${mediaCdn('docs/assets/readme-link-settings.svg')})](#settings-reference)`,
+    `[![Install](${packageMediaUrls.readmeInstall})](#installation)`,
+    `[![Quick Start](${packageMediaUrls.readmeQuickStart})](#quick-start)`,
+    `[![Commands](${packageMediaUrls.readmeCommands})](#core-commands)`,
+    `[![Settings](${packageMediaUrls.readmeSettings})](#settings-reference)`,
   ].join(' ')}\n\n**Workflow Suite Version:** `;
 
   let readme = sourceReadme.replace(
@@ -29,7 +24,7 @@ function buildPackageReadme(sourceReadme) {
     headerBlock,
   );
 
-  const packageMediaBlock = `## Quick Demo\n\nSee Pi Workflow Suite in action: structured workflow modes, settings, runtime status, and guided execution inside Pi.\n\n[![Watch the Pi Workflow Suite quick demo](${mediaCdn('docs/assets/pi-workflow-suite-demo.gif')})](${mediaCdn('docs/assets/pi-workflow-suite-demo.mp4')})\n\n## Screenshots\n\n${[
+  const packageMediaBlock = `## Quick Demo\n\nSee Pi Workflow Suite in action: structured workflow modes, settings, runtime status, and guided execution inside Pi.\n\n[![Watch the Pi Workflow Suite quick demo](${packageMediaUrls.demoGif})](${packageMediaUrls.demoMp4})\n\n## Screenshots\n\n${[
     ['Pi Workflow Suite Mission Home with workflow graphs', 'docs/assets/screenshots/00-mission-home.png'],
     ['Pi Workflow Suite startup logo', 'docs/assets/screenshots/01-startup-Logo.png'],
     ['Workflow Suite theme settings', 'docs/assets/screenshots/02-theme-settings.png'],
@@ -37,18 +32,18 @@ function buildPackageReadme(sourceReadme) {
     ['Workflow Suite shared sub-agent settings', 'docs/assets/screenshots/04-SharedSubAgentsSettings.png'],
     ['Mission Mode milestone progress', 'docs/assets/screenshots/05-mission-mode.png'],
     ['Workflow Suite Mermaid diagram output', 'docs/assets/screenshots/06-diagram-mermaid.png'],
-  ].map(([alt, path]) => `![${alt}](${mediaCdn(path)})`).join('\n\n')}\n\n`;
+  ].map(([alt, path]) => `![${alt}](${packageMediaUrl(path)})`).join('\n\n')}\n\n`;
 
   return readme.replace(/## Quick Demo[\s\S]*?## Contents\n/, `${packageMediaBlock}## Contents\n`);
 }
 
 function assertPackageReadme(readme) {
   const required = [
-    mediaCdn('docs/assets/pi-workflow-suite-header.png'),
-    mediaCdn('docs/assets/pi-workflow-suite-demo.gif'),
-    mediaCdn('docs/assets/pi-workflow-suite-demo.mp4'),
-    mediaCdn('docs/assets/screenshots/00-mission-home.png'),
-    mediaCdn('docs/assets/screenshots/06-diagram-mermaid.png'),
+    packageMediaUrls.header,
+    packageMediaUrls.demoGif,
+    packageMediaUrls.demoMp4,
+    packageMediaUrls.screenshots.missionHome,
+    packageMediaUrls.screenshots.diagramMermaid,
     '[![Watch the Pi Workflow Suite quick demo]',
   ];
   for (const needle of required) {
@@ -63,6 +58,12 @@ function assertPackageReadme(readme) {
   if (readme.includes('src="docs/assets/screenshots/') || readme.includes('](docs/assets/screenshots/')) {
     throw new Error('package README still contains source-relative screenshot paths');
   }
+  if (readme.includes('@mediadatafusion/pi-workflow-suite@0.0.6/docs/assets')) {
+    throw new Error('package README still contains old 0.0.6 package media URLs');
+  }
+  if (readme.includes('raw.githubusercontent.com/MediaDataFusion/pi-workflow-suite/v0.0.12/docs/assets')) {
+    throw new Error('package README points at raw GitHub media instead of the established jsDelivr npm CDN');
+  }
 }
 
 function looksPackageSafe(readme) {

package/scripts/quarantine-live-junk.sh

@@ -54,7 +54,7 @@ while IFS= read -r -d '' path; do
       ;;
   esac
   move_rel "$rel"
-done < <(find "$LIVE_DIR" -maxdepth 3 \( -name '*.backup.*' -o -name '*.broken.*' -o -name '.DS_Store' -o -name '*.log' \) -print0 2>/dev/null)
+done < <(find "$LIVE_DIR" -maxdepth 3 \( -name '*.bak' -o -name '*.backup.*' -o -name '*.broken.*' -o -name '.DS_Store' -o -name '*.log' \) -print0 2>/dev/null)
 
 # Known stale/development directories from earlier manual repair flows. These are
 # quarantined whole only when present. Review the dry-run output first.

package/scripts/verify-live.sh

@@ -37,13 +37,21 @@ warn_stale_files() {
 
 warn_unexpected_loadable_extensions() {
   local expected actual unexpected
+  # Keep aligned with package/runtime extension-surface files. Some helper
+  # modules have no-op default exports so Pi's broad discovery can load them
+  # safely; they are intentional live files, not stale extension candidates.
   expected="$(cat <<'TEXT'
 extensions/subagent/index.ts
 extensions/workflow-model-router.ts
 extensions/workflow-modes.ts
+extensions/workflow-parsers.ts
+extensions/workflow-settings-capabilities.ts
 extensions/workflow-state.ts
+extensions/workflow-subagent-policy.ts
 extensions/workflow-summary.ts
 extensions/workflow-tool-guard.ts
+extensions/workflow-validation-classifier.ts
+extensions/workflow-web-tools.ts
 TEXT
 )"
   actual="$(
@@ -54,7 +62,7 @@ TEXT
   )"
   unexpected="$(comm -13 <(printf '%s\n' "$expected" | sort) <(printf '%s\n' "$actual" | sort) || true)"
   if [[ -n "$unexpected" ]]; then
-    printf 'warning: unexpected loadable extension candidates found:\n%s\n' "$unexpected" >&2
+    printf 'warning: unexpected files in extension load surface found:\n%s\n' "$unexpected" >&2
     warning=1
   fi
 }

package/skills/implementation-planning/SKILL.md

@@ -5,7 +5,7 @@ description: Convert a user task into an execution-ready implementation plan wit
 
 # Implementation Planning
 
-Produce concrete plans only. Ask follow-up questions when required. Include task summary, assumptions, files likely to change, off-limits files, implementation steps, risks, validation steps, rollback notes, and readiness status.
+Produce concrete plans only. Ask follow-up questions when required. Include task summary, assumptions, files likely to change, allowed new file locations, off-limits files, implementation steps, risks, validation steps, rollback notes, and readiness status. Do not plan arbitrary repository-root files unless the exact root path is approved and justified; otherwise route new artifacts to conventional project directories.
 
 Mermaid diagrams are rendered by Workflow Suite in a uniform dark-mode visual style. For user-facing workflows, export/share paths, request lifecycles, architecture, data flow, multi-step sequences, state transitions, dependencies, validation flow, or implementation phases, include a meaningful Mermaid diagram plus concise prose unless the user requested prose only or the response is trivial. Use concise labels and the right diagram type; do not hardcode random style/classDef/light-theme overrides unless the user explicitly asks.
 ## Professional Constraints

package/skills/safe-execution/SKILL.md

@@ -5,7 +5,7 @@ description: Keep code changes bound to an approved plan, avoid unrelated refact
 
 # Safe Execution
 
-Execute only the approved plan. Restate expected files before editing. Prefer surgical edits. Do not commit, push, switch branches, install dependencies, deploy, or run destructive commands. Stop and ask if the approved plan is insufficient.
+Execute only the approved plan. Restate expected files and allowed new file locations before editing. Prefer surgical edits. Do not create arbitrary repository-root files; a root file requires an exact approved root path. Inspect project conventions and use established source, test, docs, config, script, or feature-local directories. If a current-task-created file is misplaced, preserve and move it to the correct approved path instead of deleting it. Treat untracked or unexpected files as possibly user-owned and stop/report before moving or deleting them. Do not commit, push, switch branches, install dependencies, deploy, or run destructive commands. Stop and ask if the approved plan is insufficient.
 
 Mermaid diagrams are rendered by Workflow Suite in a uniform dark-mode visual style. For user-facing workflows, export/share paths, request lifecycles, architecture, data flow, multi-step sequences, state transitions, dependencies, validation flow, or implementation phases, include a meaningful Mermaid diagram plus concise prose unless the user requested prose only or the response is trivial. Use concise labels and the right diagram type; do not hardcode random style/classDef/light-theme overrides unless the user explicitly asks.
 ## Professional Constraints

package/skills/validation-review/SKILL.md

@@ -5,7 +5,7 @@ description: Review implementation against an approved plan and return PASS, PAR
 
 # Validation Review
 
-Use read-only review. Compare changed files and implementation behavior against the approved plan. Report PASS, PARTIAL PASS, or FAIL. Include coverage, missing requirements, unexpected changes, regression risks, test/build status, and next action.
+Use read-only review. Compare changed files and implementation behavior against the approved plan. Report PASS, PARTIAL PASS, or FAIL. Include coverage, missing requirements, unexpected changes, regression risks, test/build status, and next action. Flag arbitrary repository-root files, misplaced files, unsafe cleanup-by-deletion, and deleted recoverable files unless the exact path/disposition was approved. Do not repair, move, delete, or write project source files during validation review.
 
 Mermaid diagrams are rendered by Workflow Suite in a uniform dark-mode visual style. For user-facing workflows, export/share paths, request lifecycles, architecture, data flow, multi-step sequences, state transitions, dependencies, validation flow, or implementation phases, include a meaningful Mermaid diagram plus concise prose unless the user requested prose only or the response is trivial. Use concise labels and the right diagram type; do not hardcode random style/classDef/light-theme overrides unless the user explicitly asks.
 ## Professional Constraints