fraim 2.0.363-next.1 → 2.0.364-next.0

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/publish-mcp-app.md

@@ -6,14 +6,16 @@
 Publish and distribute a Model Context Protocol (MCP) server application to major AI marketplaces and app stores (like ChatGPT and Claude).
 
 ## Outcome
-- The MCP app is successfully submitted for approval to all targeted platforms.
-- A status report detailing the submission state, verification challenges, and expected wait times.
+- A reviewable submission package per targeted platform (assets, listing details, verification plan) at `docs/mcp-publishing/{appName}-submission-plan-{YYYY-MM-DD}.md`.
+- After the manager selects `approve_and_publish`, the MCP app is submitted for approval to all targeted platforms, with a status report detailing the submission state, verification challenges, and expected wait times.
 
 ## Steps
-1. Phase 1: `verify-assets`
-2. Phase 2: `publishing-review`
-3. Phase 3: `execute-publishing`
-4. Phase 4: `retrospective`
+1. Phase 1: `scoping`
+2. Phase 2: `verify-assets`
+3. Phase 3: `prepare-submissions`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/dev-ops/setup-remote-hub.md

@@ -16,8 +16,9 @@ Provision a remote machine, install the FRAIM Hub runtime, and register it as a
 3. Phase 3: `install`
 4. Phase 4: `configure`
 5. Phase 5: `start`
-6. Phase 6: `register`
-7. Phase 7: `retrospective`
+6. Phase 6: `submit`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/engineering/mobile-app-rejection-response.md

@@ -3,11 +3,12 @@
 # FRAIM Job: mobile-app-rejection-response
 
 ## Intent
-Respond to an app store rejection — analyze the cited guideline / policy, gather evidence, draft a Resolution Center / Policy Center reply, post it, and decide next steps (clarify-and-resubmit, ship a fixed binary, or escalate via App Review Board / Play appeal). Single job parameterized by `platform` — composes Apple-specific or Play-specific guidance based on a Phase 1 decision. Reused on every rejection cycle. Triggered from `mobile-app-submission` → `monitor-and-respond` when a rejection is received.
+Respond to an app store rejection — analyze the cited guideline / policy, gather evidence, draft a Resolution Center / Policy Center reply, post it, and decide next steps (clarify-and-resubmit, ship a fixed binary, or escalate via App Review Board / Play appeal). Single job parameterized by `platform` — composes Apple-specific or Play-specific guidance based on a Phase 1 decision. Reused on every rejection cycle. Triggered when a rejection is received for a version submitted through `mobile-app-submission`.
 
 ## Outcome
-- **A Posted Reply**: A Resolution Center (iOS) or Policy Center (Android) message responding to the rejection is sent.
-- **A Clear Decision**: One of three paths chosen and acted on: (a) Clarify-and-Resubmit, (b) Ship a Fixed Binary, (c) Escalate (App Review Board / Play appeal).
+- **A Reviewed Reply**: A drafted Resolution Center (iOS) or Policy Center (Android) reply with its evidence and a next-step plan, reviewed by the manager before anything is sent.
+- **A Posted Reply**: After the manager selects `approve_and_post_reply`, the reply is posted to the store thread.
+- **A Clear Plan**: One of three paths recorded for after the platform responds: (a) Clarify-and-Resubmit, (b) Ship a Fixed Binary, (c) Escalate (App Review Board / Play appeal).
 - **Audit Trail**: The full rejection thread, evidence collected, and decision rationale captured in `docs/<store>/rejections/<submission-id>.md`.
 
 ## Steps
@@ -17,9 +18,7 @@ Respond to an app store rejection — analyze the cited guideline / policy, gath
 4. Phase 4: `response-drafting`
 5. Phase 5: `submit`
 6. Phase 6: `address-feedback`
-7. Phase 7: `post-reply`
-8. Phase 8: `re-evaluate-resubmit-or-appeal`
-9. Phase 9: `retrospective`
+7. Phase 7: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/engineering/mobile-app-submission.md

@@ -6,10 +6,11 @@
 Submit a mobile binary to the destination app store. Single job parameterized by `platform` — composes the App Store Connect (iOS) or Google Play Console (Android) flow based on a Phase 1 decision. Reused on every release. Covers the store-side end-to-end: metadata, screenshots, privacy disclosures, demo creds (where applicable), reviewer notes, and the actual Submit-for-Review click. Routes any rejection into `mobile-app-rejection-response`.
 
 ## Outcome
-- **Submitted Version**: A store version is in `Waiting for Review` / `In Review` / `In review` status with all required fields filled and one binary attached.
+- **Ready Version**: A store version with all required fields filled and one binary attached, reviewed by the manager before submission.
+- **Submitted Version**: After the manager selects `approve_and_submit`, the version is in `Waiting for Review` / `In Review` / `In review` status.
 - **Demo-Ready Account** (sign-in apps only): Synthetic reviewer account exists and is seeded with realistic data.
 - **Submission Audit Trail**: A submission ID, build/version code, and complete log of fields filled in the project's evidence dir.
-- **Monitoring Hook**: Either approval is recorded, or the rejection routes into `mobile-app-rejection-response` with full context preserved.
+- **Monitoring Hook**: The submission identity and expected review window are recorded; a rejection routes into `mobile-app-rejection-response` with full context preserved.
 
 ## Steps
 1. Phase 1: `platform-selection`
@@ -20,9 +21,8 @@ Submit a mobile binary to the destination app store. Single job parameterized by
 6. Phase 6: `store-specific-fields`
 7. Phase 7: `demo-account-and-review-info`
 8. Phase 8: `submit`
-9. Phase 9: `submit-for-review`
-10. Phase 10: `monitor-and-respond`
-11. Phase 11: `retrospective`
+9. Phase 9: `address-feedback`
+10. Phase 10: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/finance/cloud-credits-application.md

@@ -16,10 +16,9 @@ Apply for startup cloud credits through one selected provider path: `aws-activat
 3. Phase 3: `navigate-to-provider`
 4. Phase 4: `sign-in-to-provider`
 5. Phase 5: `fill-application`
-6. Phase 6: `review-application`
-7. Phase 7: `submit-application`
-8. Phase 8: `verify-application-status`
-9. Phase 9: `retrospective`
+6. Phase 6: `submit`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/fraim/adhoc-prompt.md

@@ -12,11 +12,13 @@
 Run any task that does not map to a structured FRAIM catalog job. Use as a fallback when no catalog job matches the user's request — not as a substitute for a structured job when one exists. Agents must not select this job speculatively; it is offered only when no catalog match is found.
 
 ## Outcome
-The task described in the manager's instructions is complete, with a lightweight record of what happened and a recommendation on whether to formalize the task as a recurring FRAIM job.
+The task described in the manager's instructions is complete and submitted for review, with a lightweight record of what happened and a recommendation on whether to formalize the task as a recurring FRAIM job.
 
 ## Steps
 1. Phase 1: `run`
-2. Phase 2: `retrospective`
+2. Phase 2: `submit`
+3. Phase 3: `address-feedback`
+4. Phase 4: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/fraim/contribute-to-fraim.md

@@ -6,16 +6,16 @@
 Allow users to contribute their custom Jobs, Skills, Rules, and Values back to the core FRAIM project. This job asks the user which specific capabilities they want to share, packages them, and files a contribution issue in the FRAIM repository.
 
 ## Outcome
-- Final artifact: A detailed contribution issue filed in the FRAIM repository with packaged artifacts.
+- Reviewable contribution package at `docs/contributions/{name}-contribution-{YYYY-MM-DD}.md`.
+- After the manager selects `approve_and_file`, a detailed contribution issue filed in the FRAIM repository with the packaged artifacts.
 - **Improved Ecosystem**: The user's proven capabilities are shared with the broader FRAIM community.
 
 ## Steps
 1. Phase 1: `gather-contribution-intent`
 2. Phase 2: `discover-contribution-artifacts`
-3. Phase 3: `confirm-contribution-package`
-4. Phase 4: `file-contribution-issue`
-5. Phase 5: `completion`
-6. Phase 6: `retrospective`
+3. Phase 3: `submit`
+4. Phase 4: `address-feedback`
+5. Phase 5: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/fraim/file-fraim-issue.md

@@ -6,15 +6,15 @@
 File a user-readable bug report in the FRAIM repository. The agent elicits the user's own words about impact and symptoms before harvesting any technical context, then structures the issue so the user experience comes first and the technical detail comes last.
 
 ## Outcome
-- Final artifact: A new GitHub issue filed in the FRAIM repository.
+- Reviewable issue draft at `docs/fraim-issues/{YYYY-MM-DD}-{slug}.md`.
+- After the manager selects `approve_and_file`, a new GitHub issue filed in the FRAIM repository.
 - **User-Readable Report**: The issue opens with user impact and observable symptoms, followed by plain-language repro steps, with technical context appended last and omitted when nothing is found.
 
 ## Steps
 1. Phase 1: `gather-issue-details`
-2. Phase 2: `confirm-issue-details`
-3. Phase 3: `file-issue`
-4. Phase 4: `completion`
-5. Phase 5: `retrospective`
+2. Phase 2: `submit`
+3. Phase 3: `address-feedback`
+4. Phase 4: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/fraim/troubleshoot-fraim.md

@@ -14,7 +14,9 @@ Resolve a FRAIM issue the user is experiencing — connectivity, sync, Hub start
 1. Phase 1: `collect-symptom`
 2. Phase 2: `diagnose`
 3. Phase 3: `repair-or-escalate`
-4. Phase 4: `retrospective`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
 
 ---
 

package/dist/registry/stubs/jobs/ai-employee/management/project-onboarding.md

@@ -7,9 +7,9 @@ Onboard a project into a trustworthy FRAIM-ready state by reusing what FRAIM can
 
 ## Outcome
 - `fraim/config.json` contains the approved project metadata and validation settings needed for future FRAIM work.
-- `fraim/personalized-employee/context/project_context.md` captures durable project facts: what this project is, how it is structured, and what future agents should understand before working.
-- `fraim/personalized-employee/rules/project_rules.md` captures durable project-wide operating rules for future agents.
-- The user understands what FRAIM confirmed automatically, what still needs input, what can be added later, and which next FRAIM reviews or scaffolding jobs would make this specific project stronger.
+- `fraim/personalized-employee/context/project_context.md` is a short brief: the project's Objective and its Success criteria, with links to existing project documents for anything more.
+- `fraim/personalized-employee/rules/project_rules.md` holds adopted standing project expectations, with advice on reducing unnecessary startup context.
+- The user understands what FRAIM confirmed automatically, what still needs input, what changed in existing context and rules, and which first jobs fit this project and why.
 
 ## Steps
 1. Phase 0: `sync`

package/dist/src/cli/commands/workspace-config.js

@@ -4,6 +4,8 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 };
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.workspaceConfigCommand = void 0;
+exports.checkProjectBrief = checkProjectBrief;
+exports.checkProjectRules = checkProjectRules;
 exports.runWorkspaceConfigValidate = runWorkspaceConfigValidate;
 const commander_1 = require("commander");
 const fs_1 = require("fs");
@@ -16,11 +18,201 @@ function resolveConfigPath(projectRoot, explicitPath) {
     }
     return (0, project_fraim_paths_1.getWorkspaceConfigPath)(projectRoot ? path_1.default.resolve(projectRoot) : process.cwd());
 }
+// Shape of the project brief written by project-onboarding from
+// templates/manager/PROJECT-CONTEXT-TEMPLATE.md.
+const BRIEF_REQUIRED_SECTIONS = ['Objective', 'Success criteria'];
+const BRIEF_ALLOWED_SECTIONS = [...BRIEF_REQUIRED_SECTIONS, 'More detail'];
+const BRIEF_MIN_SUCCESS_ITEMS = 2;
+const BRIEF_MAX_SUCCESS_ITEMS = 4;
+const BRIEF_MAX_WORDS = 150;
+// Suggested shape of project_rules.md; adopted rules may exceed it.
+const RULES_REVIEW_GUIDANCE = 7;
+const RULES_EMPTY_FORMS = ['No project rules adopted yet.', 'No project-specific rules yet.'];
+const LIST_ITEM = /^([-*+]|\d+[.)])\s+/;
+const MARKDOWN_LINK = /\[[^\]]+\]\([^)\s]+(\s+"[^"]*")?\)/;
+function markdownLines(content) {
+    let inFence = false;
+    return content.split(/\r?\n/).map((text) => {
+        const fenceMarker = /^\s*(```|~~~)/.test(text);
+        const line = { text, inFence: inFence || fenceMarker };
+        if (fenceMarker)
+            inFence = !inFence;
+        return line;
+    });
+}
+function headingOf(line) {
+    if (line.inFence)
+        return null;
+    const match = /^(#{1,6})\s+(.*?)\s*#*\s*$/.exec(line.text);
+    return match ? { level: match[1].length, title: match[2].trim() } : null;
+}
+function countWords(lines) {
+    return lines
+        .map((line) => line.trim().replace(LIST_ITEM, ''))
+        .join(' ')
+        .split(/\s+/)
+        .filter(Boolean).length;
+}
+/**
+ * Check project_context.md against the two-section brief. Returns one message per
+ * violation; an empty array means the brief has the template shape.
+ */
+function checkProjectBrief(content) {
+    const violations = [];
+    const sections = new Map();
+    const order = [];
+    let current = null;
+    for (const line of markdownLines(content)) {
+        const heading = headingOf(line);
+        if (heading && heading.level >= 3) {
+            violations.push(`H3 or deeper heading "${heading.title}" is not allowed; use only the template's H2 sections`);
+            continue;
+        }
+        if (heading && heading.level === 2) {
+            if (!BRIEF_ALLOWED_SECTIONS.includes(heading.title)) {
+                violations.push(`heading "${heading.title}" is not allowed; allowed H2 headings are ${BRIEF_ALLOWED_SECTIONS.join(', ')}`);
+                current = null;
+                continue;
+            }
+            current = [];
+            if (!sections.has(heading.title))
+                sections.set(heading.title, []);
+            sections.get(heading.title).push(current);
+            order.push(heading.title);
+            continue;
+        }
+        if (heading && heading.level === 1) {
+            current = null;
+            continue;
+        }
+        if (current)
+            current.push(line.text);
+    }
+    for (const name of BRIEF_ALLOWED_SECTIONS) {
+        const occurrences = sections.get(name)?.length ?? 0;
+        if (occurrences === 0 && BRIEF_REQUIRED_SECTIONS.includes(name)) {
+            violations.push(`section "${name}" is missing`);
+        }
+        if (occurrences > 1)
+            violations.push(`section "${name}" appears more than once`);
+    }
+    const objectiveAt = order.indexOf('Objective');
+    const successAt = order.indexOf('Success criteria');
+    if (objectiveAt >= 0 && successAt >= 0 && successAt < objectiveAt) {
+        violations.push('section "Objective" must come before "Success criteria"');
+    }
+    const successLines = (sections.get('Success criteria') ?? []).flat();
+    const successItems = successLines.filter((line) => LIST_ITEM.test(line)).length;
+    if (sections.has('Success criteria') && (successItems < BRIEF_MIN_SUCCESS_ITEMS || successItems > BRIEF_MAX_SUCCESS_ITEMS)) {
+        violations.push(`section "Success criteria" has ${successItems} list item${successItems === 1 ? '' : 's'}; ` +
+            `it needs ${BRIEF_MIN_SUCCESS_ITEMS} to ${BRIEF_MAX_SUCCESS_ITEMS}`);
+    }
+    const words = countWords([...(sections.get('Objective') ?? []).flat(), ...successLines]);
+    if (words > BRIEF_MAX_WORDS) {
+        violations.push(`"Objective" and "Success criteria" together have ${words} words; the limit is ${BRIEF_MAX_WORDS}`);
+    }
+    const detailLines = (sections.get('More detail') ?? []).flat().filter((line) => line.trim());
+    detailLines.forEach((line, index) => {
+        if (!LIST_ITEM.test(line.trim()) || !MARKDOWN_LINK.test(line)) {
+            violations.push(`section "More detail" line ${index + 1} is not a list item with a Markdown link`);
+        }
+    });
+    return violations;
+}
+/**
+ * Return advisory deviations from the concise project-rules template.
+ * These findings never reject adopted rules or authorize rewriting them.
+ */
+function checkProjectRules(content) {
+    const warnings = [];
+    let ruleCount = 0;
+    let awaitingWhy = false;
+    let spansReported = false;
+    let emptyForm = false;
+    const closeRule = () => {
+        if (ruleCount > 0 && awaitingWhy)
+            warnings.push(`rule ${ruleCount} has no "Why:" line`);
+    };
+    for (const line of markdownLines(content)) {
+        const trimmed = line.text.trim();
+        if (!trimmed)
+            continue;
+        const heading = headingOf(line);
+        if (heading && heading.level >= 2) {
+            warnings.push(`heading "${heading.title}" differs from the suggested flat numbered list`);
+            continue;
+        }
+        if (heading)
+            continue;
+        if (/^\d+[.)]\s+\S/.test(trimmed) && !line.inFence) {
+            closeRule();
+            ruleCount += 1;
+            awaitingWhy = true;
+            spansReported = false;
+            continue;
+        }
+        if (RULES_EMPTY_FORMS.includes(trimmed)) {
+            emptyForm = true;
+            continue;
+        }
+        if (ruleCount === 0)
+            continue;
+        if (awaitingWhy && /^Why:/.test(trimmed)) {
+            awaitingWhy = false;
+            continue;
+        }
+        if (!spansReported) {
+            warnings.push(`rule ${ruleCount} spans more than one line; consider shortening it if the extra detail is unnecessary`);
+            spansReported = true;
+        }
+    }
+    closeRule();
+    if (ruleCount > RULES_REVIEW_GUIDANCE)
+        warnings.push(`${ruleCount} numbered rules; above the review guidance of ${RULES_REVIEW_GUIDANCE}, but more are allowed`);
+    if (ruleCount === 0 && !emptyForm) {
+        warnings.push(`neither numbered rules nor the empty-form sentence "${RULES_EMPTY_FORMS[0]}"`);
+    }
+    return warnings;
+}
+function checkProjectArtifacts(projectRoot, includeBrief) {
+    const artifacts = [
+        ...(includeBrief ? [{ file: 'project_context.md', directory: 'context', check: checkProjectBrief, advisory: false }] : []),
+        { file: 'project_rules.md', directory: 'rules', check: checkProjectRules, advisory: true }
+    ];
+    const violations = [];
+    const warnings = [];
+    for (const artifact of artifacts) {
+        const filePath = (0, project_fraim_paths_1.getWorkspaceFraimPath)(projectRoot, 'personalized-employee', artifact.directory, artifact.file);
+        if (!(0, fs_1.existsSync)(filePath)) {
+            violations.push(artifact.file + ': file is missing');
+            continue;
+        }
+        const findings = artifact.check((0, fs_1.readFileSync)(filePath, 'utf8')).map((finding) => artifact.file + ': ' + finding);
+        (artifact.advisory ? warnings : violations).push(...findings);
+    }
+    return { violations, warnings };
+}
 function runWorkspaceConfigValidate(options) {
     const configPath = resolveConfigPath(options.projectRoot, options.configPath);
     const rawConfig = JSON.parse((0, fs_1.readFileSync)(configPath, 'utf8'));
     (0, fraim_config_contract_1.assertValidWorkspaceFraimConfig)(rawConfig);
     console.log(`Validated ${path_1.default.relative(process.cwd(), configPath) || (0, project_fraim_paths_1.getWorkspaceFraimDisplayPath)('config.json')}`);
+    if (!options.projectArtifacts && !options.projectRules)
+        return;
+    const projectRoot = options.projectRoot ? path_1.default.resolve(options.projectRoot) : process.cwd();
+    const { violations, warnings } = checkProjectArtifacts(projectRoot, Boolean(options.projectArtifacts));
+    for (const warning of warnings)
+        console.warn(`Warning: ${warning}`);
+    if (warnings.length > 0) {
+        console.warn('Warning: Extra rule text is read at startup and can slow starting. Review unnecessary detail or duplication; you may keep these rules.');
+    }
+    if (violations.length > 0) {
+        for (const violation of violations)
+            console.error(violation);
+        process.exitCode = 1;
+        return;
+    }
+    console.log(options.projectArtifacts ? 'Validated project_context.md and checked project_rules.md' : 'Checked project_rules.md');
 }
 exports.workspaceConfigCommand = new commander_1.Command('workspace-config')
     .description('Deterministically validate workspace fraim/config.json')
@@ -28,4 +220,6 @@ exports.workspaceConfigCommand = new commander_1.Command('workspace-config')
     .description('Validate fraim/config.json against the shared workspace config contract')
     .option('--project-root <path>', 'Project root used to resolve fraim/config.json')
     .option('--config-path <path>', 'Explicit path to fraim/config.json')
+    .option('--project-artifacts', 'Also validate the brief and report advisory project-rule checks')
+    .option('--project-rules', 'Check project rules only, with advisory count and format warnings')
     .action((options) => runWorkspaceConfigValidate(options)));

package/dist/src/cli/utils/agent-adapters.js

@@ -77,7 +77,7 @@ This repository uses FRAIM.
 - If no exact or high-confidence job match exists, say that no FRAIM job matches and continue with normal tools or ask one concise clarification.
 - For deeper capability detail, call \`get_fraim_file({ path: "skills/<category>/<skill-name>.md" })\` or \`get_fraim_file({ path: "rules/<category>/<rule-name>.md" })\`.
 - Read \`${projectRulesPath}\` if it exists before doing work.
-- When users ask for next step recommendations, use recommend-next-job skill under \`${employeeSkillsPath}/\` to gather context before suggesting jobs.
+- When users ask for next step recommendations, use recommend-project-priorities skill under \`${employeeSkillsPath}/\` to gather context before suggesting jobs.
 - ${ide_invocation_surfaces_1.FRAIM_MCP_UNAVAILABLE_MANAGER_GUIDANCE}
 
 > [!IMPORTANT]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fraim",
-  "version": "2.0.363-next.1",
+  "version": "2.0.364-next.0",
   "description": "FRAIM core CLI and MCP package.",
   "main": "index.js",
   "bin": {