@mriekki/project-forge 3.0.0 → 4.0.0

package/assets/components.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "package": "@mriekki/project-forge",
-  "version": "3.0.0",
+  "version": "4.0.0",
   "defaultProfile": "greenfield-project",
   "profiles": {
     "greenfield-project": {
@@ -14,8 +14,8 @@
   "components": {
     "core": {
       "repository": "mriekki/project-forge-core",
-      "commit": "17a09fc913a12902c4a9172e53bc70d421f5b0d5",
-      "version": "3.3.0",
+      "commit": "e20e9b0e7102477a30bc15a771d62ba537efe60c",
+      "version": "4.0.0",
       "distribution": "greenfield-workspace",
       "descriptor": "assets/core/distribution.json",
       "sourceRoot": "assets/generated/core",

package/assets/core/distribution.json

@@ -4,12 +4,10 @@
   "profileDestination": ".github/project-forge-workspace.json",
   "mappings": [
     {"source":"core/agents/reviewer.agent.md","destination":".github/agents/reviewer.agent.md"},
-    {"source":"core/agents/coach.agent.md","destination":".github/agents/coach.agent.md"},
     {"source":"core/instructions/project-forge-workflow.instructions.md","destination":".github/instructions/project-forge-workflow.instructions.md"},
     {"source":"core/instructions/project-forge-docs.instructions.md","destination":".github/instructions/project-forge-docs.instructions.md"},
     {"source":"core/skills/define-feature/SKILL.md","destination":".github/skills/define-feature/SKILL.md"},
     {"source":"core/skills/grill-me/SKILL.md","destination":".github/skills/grill-me/SKILL.md"},
-    {"source":"core/skills/grill-with-docs/SKILL.md","destination":".github/skills/grill-with-docs/SKILL.md"},
     {"source":"core/skills/refine-requirements/SKILL.md","destination":".github/skills/refine-requirements/SKILL.md"},
     {"source":"core/skills/start-work/SKILL.md","destination":".github/skills/start-work/SKILL.md"},
     {"source":"core/skills/setup/SKILL.md","destination":".github/skills/setup/SKILL.md"},
@@ -23,10 +21,8 @@
     {"source":"core/skills/cleanup-branches/SKILL.md","destination":".github/skills/cleanup-branches/SKILL.md"},
     {"source":"core/skills/pull-latest/SKILL.md","destination":".github/skills/pull-latest/SKILL.md"},
     {"source":"core/skills/project-forge-update/SKILL.md","destination":".github/skills/project-forge-update/SKILL.md"},
-    {"source":"core/skills/core-sync/SKILL.md","destination":".github/skills/core-sync/SKILL.md"},
     {"source":"core/skills/upstream-fix/SKILL.md","destination":".github/skills/upstream-fix/SKILL.md"},
     {"source":"core/skills/wait-what/SKILL.md","destination":".github/skills/wait-what/SKILL.md"},
-    {"source":"core/skills/developer-env-mode/SKILL.md","destination":".github/skills/developer-env-mode/SKILL.md"},
     {"source":"core/skills/deployment-readiness/SKILL.md","destination":".github/skills/deployment-readiness/SKILL.md"},
     {"source":"core/skills/deploy/SKILL.md","destination":".github/skills/deploy/SKILL.md"},
     {"source":"core/skills/tear-down/SKILL.md","destination":".github/skills/tear-down/SKILL.md"},

package/assets/generated/ASSEMBLY.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
   "package": "@mriekki/project-forge",
-  "version": "3.0.0",
+  "version": "4.0.0",
   "components": {
     "core": {
       "repository": "mriekki/project-forge-core",
-      "commit": "17a09fc913a12902c4a9172e53bc70d421f5b0d5",
-      "version": "3.3.0",
+      "commit": "e20e9b0e7102477a30bc15a771d62ba537efe60c",
+      "version": "4.0.0",
       "distribution": "greenfield-workspace",
       "files": [
         {
@@ -19,15 +19,10 @@
           "destination": ".github/agents/reviewer.agent.md",
           "sha256": "94255c72a6c875722ebaf8b0cb328fe019856c01443b550ca6e2f6c422da983e"
         },
-        {
-          "source": "core/agents/coach.agent.md",
-          "destination": ".github/agents/coach.agent.md",
-          "sha256": "f2da3ed8ba1890f0886615c0d7a66411265524dcaf04648ef10dfd195dde522e"
-        },
         {
           "source": "core/instructions/project-forge-workflow.instructions.md",
           "destination": ".github/instructions/project-forge-workflow.instructions.md",
-          "sha256": "aa03af8ef23d32d90a85adaeb549873e4de32798c58bfdaf7fe4183a549b1a17"
+          "sha256": "a6b28d916b67c9eec3831e414b56be3636512f7f7740523d22aaaf6efa00d335"
         },
         {
           "source": "core/instructions/project-forge-docs.instructions.md",
@@ -42,12 +37,7 @@
         {
           "source": "core/skills/grill-me/SKILL.md",
           "destination": ".github/skills/grill-me/SKILL.md",
-          "sha256": "d3c9885e1b32feeb940403a4c890f7ac552b7e9648a2589adb2cfabe33e19182"
-        },
-        {
-          "source": "core/skills/grill-with-docs/SKILL.md",
-          "destination": ".github/skills/grill-with-docs/SKILL.md",
-          "sha256": "facdfecee977ab01bbe908f6f122e483ea27c98a8f1562973f59f9266b63323e"
+          "sha256": "a71c2dcf63d7d88beb9112fcfe0cf19dbc233934f30bbe95727f58b29e845ffb"
         },
         {
           "source": "core/skills/refine-requirements/SKILL.md",
@@ -57,12 +47,12 @@
         {
           "source": "core/skills/start-work/SKILL.md",
           "destination": ".github/skills/start-work/SKILL.md",
-          "sha256": "5f4d46323d19bb7a1d4e64f233ae64aae8e1874da072d38cb344d3d834bdea8e"
+          "sha256": "f054edd5a745489623579d25e334f5fcd6cebd6e73b86970074e7c2444f9af40"
         },
         {
           "source": "core/skills/setup/SKILL.md",
           "destination": ".github/skills/setup/SKILL.md",
-          "sha256": "60dcb93e98f6f00177e9e2d406c55f15bd59ebf8607c3f79ae464fe7c00616b6"
+          "sha256": "2f1b88b31b2c7233a00ab9293cd98a5fade00e114e1a442a793affbc7fe4ad83"
         },
         {
           "source": "core/skills/build/SKILL.md",
@@ -114,11 +104,6 @@
           "destination": ".github/skills/project-forge-update/SKILL.md",
           "sha256": "3463a68171fa30ef10f1ca514424236317ec364f015c5446f49911a1a3c9bb12"
         },
-        {
-          "source": "core/skills/core-sync/SKILL.md",
-          "destination": ".github/skills/core-sync/SKILL.md",
-          "sha256": "cbc498597cea7a48004fc507f9a6efc130544e57f347c0efdbb073f71f14965e"
-        },
         {
           "source": "core/skills/upstream-fix/SKILL.md",
           "destination": ".github/skills/upstream-fix/SKILL.md",
@@ -129,11 +114,6 @@
           "destination": ".github/skills/wait-what/SKILL.md",
           "sha256": "dba3aa4f042b813de960b60c47ae4c8a3dccb72fdc89c597fe04b720b27f5316"
         },
-        {
-          "source": "core/skills/developer-env-mode/SKILL.md",
-          "destination": ".github/skills/developer-env-mode/SKILL.md",
-          "sha256": "2e45e00e30f17edda5b259bd24852233d2bcace46f7e095d3b28faf9ce35cedb"
-        },
         {
           "source": "core/skills/deployment-readiness/SKILL.md",
           "destination": ".github/skills/deployment-readiness/SKILL.md",
@@ -207,7 +187,7 @@
         {
           "source": "core/process/INTERACTIVE_SESSION_GUIDE.md",
           "destination": "docs/process/INTERACTIVE_SESSION_GUIDE.md",
-          "sha256": "c35f2f4bc1b52746b205eab65982b32d9a2fe58f1c750f9744ddfdd320c3f52c"
+          "sha256": "8cd74fbd7433969923299849eb89bdd774fd4af1b9694639f0b9871a1047cacf"
         },
         {
           "source": "core/process/COACHING_GUIDE.md",
@@ -242,7 +222,7 @@
         {
           "source": "core/process/OPERATION_JOURNAL.md",
           "destination": "docs/process/OPERATION_JOURNAL.md",
-          "sha256": "16e2d502d7b0f923b4ea2e34bdcaaed73cdc0933fd6ef54a1278dd25f25b5140"
+          "sha256": "7051e4554ee6f3cca1b7ee8105ad1ab9f2cde4f1afc7d0f39e310144df45f390"
         },
         {
           "source": "core/process/PROJECT_REQUIREMENTS_EXPORT.md",

package/assets/generated/core/core/instructions/project-forge-workflow.instructions.md

@@ -18,7 +18,7 @@ Once a bounded action is authorized, routine mechanics inside that scope should
 
 For implementation, establish the repository-appropriate short-lived work branch as routine setup once implementation itself is authorized; do not add a separate branch-creation gate when branch policy/naming and scope are clear.
 
-Continuous modes such as `/grill-me`, `/grill-with-docs`, `/refine-requirements`, `/coach`, `/learning-review`, and `/deployment-readiness` continue until stopped or naturally complete.
+Continuous modes such as `/grill-me`, `/refine-requirements`, `/coach`, `/learning-review`, and `/deployment-readiness` continue until stopped or naturally complete.
 
 During interactive questioning, prefer concise choice-first options for genuinely bounded human decisions, including `Other / specify` and `Not sure — recommend one` when appropriate. When the host exposes native structured question controls, use them instead of a plain numbered chat list. In VS Code, use the host's structured question surface such as `vscode_askQuestions` when available: single-select for mutually exclusive decisions/actions and multi-select only when several simultaneous selections are valid. A textual numbered menu is only the fallback when structured choice UI is unavailable.
 
@@ -26,11 +26,17 @@ Make a recommendation only when current evidence, repository policy, or a clear
 
 Keep factual/environment-specific values and questions intended to elicit the human's own framing, reasoning, debugging approach, design rationale, or understanding open-ended unless options are later useful as scaffolding.
 
+`/grill-me` is the single adversarial-questioning entry point. It begins read-only and may, after one explicit session-level choice, reconcile resolved decisions into permitted local authorities or proposed external updates. Do not create a second documentation-aware grilling command.
+
+`/setup` is the single workstation/environment preparation entry point. It owns status, repair, verified local runtime convergence, remote-enabled capability preparation, and named-environment setup/proof. Do not create a second developer-environment-mode command. `/deployment-readiness <environment>` remains the later exact-environment pre-deploy verification step.
+
 For deployment readiness, inspect existing non-secret configuration before asking setup questions. Show already-known simple machine facts such as hostname/address, deployment user, port, and target OS for confirmation. Ask only for missing or conflicting facts. Keep deployment-tool implementation identifiers such as logical target names, `targetName`, SSH aliases, profile paths, and trust-file paths internal unless troubleshooting or genuine ambiguity requires them.
 
 Shared managed code keeps its canonical owner. When a consumer contains `CORE_BASELINE.json` or `DEPLOYMENT_BASELINE.json`, treat those baselines as ownership evidence. A temporary edit to a shared-managed consumer file may be used to diagnose or prove a reusable defect, but it is not the canonical deliverable.
 
-Before consumer delivery, run available managed-baseline integrity checks. If Core- or Deployment-Kit-managed files have unexplained local drift, stop before staging/commit/push and route the reusable change through `/upstream-fix`. Fix the owning canonical repository, deliver/merge it there under normal gates, then adopt the exact accepted shared commit back into the consumer through the appropriate sync mechanism and retest in consumer context.
+Before consumer delivery, run available managed-baseline integrity checks. If Core- or Deployment-Kit-managed files have unexplained local drift, stop before staging/commit/push and route the reusable change through `/upstream-fix`. Fix the owning canonical repository, deliver/merge it there under normal gates, then adopt the exact accepted shared commit back into the consumer through the appropriate update boundary and retest in consumer context.
+
+Package-managed generated Projects use `/project-forge-update`. Direct `/core-sync` remains only for component-only Core consumers without `PROJECT_FORGE_BASELINE.json` and is not part of the normal greenfield Project command surface.
 
 Do not manually preserve a private consumer fork of shared managed code merely because the consumer exposed the bug. Consumer-owned product/application files remain normal consumer implementation scope.
 

package/assets/generated/core/core/process/INTERACTIVE_SESSION_GUIDE.md

@@ -4,7 +4,6 @@ The following modes are continuous after the human explicitly enters them:
 
 ```text
 /grill-me
-/grill-with-docs
 /refine-requirements
 /coach
 /learning-review
@@ -85,7 +84,7 @@ Stop when:
 
 Continuous conversation never implies permission for unrelated file, Git, external-system, remote, or production writes.
 
-For modifying sessions such as requirement refinement or deployment-readiness documentation, one explicit session-level authorization may cover focused updates within the defined scope; do not re-ask after every answer.
+For modifying sessions such as `/grill-me` decision reconciliation, requirement refinement, or deployment-readiness documentation, one explicit session-level authorization may cover focused updates within the defined scope; do not re-ask after every answer.
 
 Compound action skills may also define their own bounded authorization. In particular, manually invoking `/deliver` after its prerequisites are satisfied authorizes routine branch/stage/commit/push/PR/CI mechanics within the accepted delivery scope. Do not interrupt that compound action with repeated ceremonial permission prompts. `/deliver` still stops for changed evidence, ambiguity/risk, and the explicit merge/finalize decision.
 

package/assets/generated/core/core/process/OPERATION_JOURNAL.md

@@ -47,11 +47,10 @@ Operation journals are workstation-local and must remain ignored by Git. They ar
 
 Journal deterministic operations when durable local diagnostics materially help:
 
-- `/setup` and repository-local setup/doctor execution;
+- `/setup` and repository-local setup/doctor execution, including local runtime convergence and remote-enabled environment preparation;
 - `/build` when build diagnostics/artifact evidence are useful;
 - `/run` as a concise startup/health receipt when useful, not as an unbounded application log sink;
 - `/project-forge-update` apply/verification work;
-- `/developer-env-mode` when it mutates or converges local runtime state;
 - `/deployment-readiness` when it performs preparation or repair;
 - environment proof operations;
 - `/deploy` and `/tear-down`;

package/assets/generated/core/core/skills/grill-me/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: grill-me
-description: Continuously challenge requirements, architecture, plans, implementation assumptions, or work-item coverage without editing files.
+description: Continuously challenge requirements, architecture, plans, implementation assumptions, or work-item coverage, with optional session-level reconciliation of resolved decisions into permitted authorities.
 argument-hint: "<work-item ID, external key, document, plan, or topic>"
 user-invocable: true
 disable-model-invocation: true
@@ -8,70 +8,108 @@ disable-model-invocation: true
 
 # Grill Me
 
-Purpose: improve reasoning by challenging the highest-value uncertainty without adding process overhead.
+Purpose: improve reasoning by challenging the highest-value uncertainty without adding process overhead or forcing the developer to choose a separate documentation-aware grilling command.
 
-## Rules
+Invocation begins read-only.
 
-- Read `.github/project-forge-workspace.json` when present and only the minimum relevant context.
-- Ask one material question at a time.
-- Explain briefly why the question matters.
-- Challenge vague answers, hidden scope, contradictions, and weak assumptions.
-- Recommend an answer or 2–3 options with tradeoffs when useful.
-- Do not edit files.
-- Do not invoke subagents.
-- Do not create artifacts merely because grilling occurred.
-- Do not claim external Jira/Issue content was read unless it was actually available.
+## 1. Resolve authority and minimum context
 
-Challenge areas may include:
-- missing acceptance behavior,
-- cross-work-item/Epic gaps,
-- domain/business rules,
-- lifecycle/state transitions,
-- validation/failure behavior,
-- data integrity,
-- concurrency/transactions,
-- destructive/reversible actions,
-- architecture assumptions,
-- security/operational risk,
-- testability.
+Read `.github/project-forge-workspace.json` when present and only the minimum relevant context.
 
-## Cadence
+Determine when applicable:
+- the authoritative work-item source;
+- which local documents are authoritative, supplemental, read-only, or not used;
+- relevant accepted ADR/design rules;
+- whether an external write integration is actually available and permitted.
 
-```text
-QUESTION
-<one focused question>
+Never assume Product/Feature Briefs exist. Never assume `Jira Epic == Feature Brief`. Do not claim external Jira/Issue content was read unless it was actually available.
 
-WHY IT MATTERS
-<short explanation>
+## 2. Continuous grilling
 
-RECOMMENDATION
-<recommended answer/options when useful>
-```
+Ask one material question at a time. Explain briefly why the question matters. Challenge vague answers, hidden scope, contradictions, and weak assumptions.
+
+Challenge areas may include:
+- missing acceptance behavior;
+- cross-work-item/Epic gaps;
+- domain/business rules;
+- lifecycle/state transitions;
+- validation/failure behavior;
+- data integrity;
+- concurrency/transactions;
+- destructive/reversible actions;
+- architecture assumptions;
+- security/operational risk;
+- accessibility/UX implications when relevant;
+- testability.
+
+When the purpose is to expose or strengthen the human's reasoning, ask open-ended first. For a bounded decision with a small credible option set, follow `INTERACTIVE_SESSION_GUIDE.md`: use host-native single-select structured choice UI for mutually exclusive alternatives when available, multi-select only when several selections are valid together, and preserve free-text/`Other / specify` when choices may be incomplete.
 
-After the human answers:
+Recommend at most one answer/option only when current evidence or a clear engineering tradeoff supports it. A recommendation is advice, not an accepted decision.
+
+Cadence:
 
 ```text
-analyze/challenge the answer
+question
+→ human answer
+→ challenge/analyze the answer
 → explain implications when useful
-→ ask the next material question
+→ reconcile the resolved decision when the session is authorized to do so
+→ next material question
 ```
 
 Do not ask `Do you want to continue?` after each answer. The human already entered a continuous grilling mode.
 
-Stop only when:
-- the human says stop/done/pause,
-- no material issues remain,
-- a true scope/decision/action gate appears,
+## 3. Optional decision reconciliation
+
+Grilling does not require document writes. When resolved decisions would benefit from durable reconciliation, present one session-level **single-select structured choice** through the host UI when available. In VS Code use the native question surface such as `vscode_askQuestions`.
+
+Offer:
+- `Continue grilling only` `[READ ONLY]` — default when no durable update is needed;
+- `Reconcile resolved decisions during this session` `[MODIFIES DOCS]`;
+- `Stop` `[NO ACTION]`.
+
+Use a numbered text list only when structured choice UI is unavailable.
+
+Selecting `Reconcile resolved decisions during this session` authorizes only focused updates to the permitted current work-item documents for this active session. Do not ask again after every answer.
+
+When a decision is resolved:
+- update an existing permitted local authority/supplement only when this session has document-write authorization;
+- if Jira/GitHub/another external system is authoritative and no permitted write integration is available, accumulate a concise `PROPOSED EXTERNAL WORK-ITEM UPDATE`;
+- if a permitted external write integration exists, require an explicit `[EXTERNAL WRITE]` choice before writing externally;
+- never create a competing local source merely to store an answer.
+
+For local-document models, common homes are:
+- brief: high-level scope/outcome/major rule;
+- combined requirements: detailed user/engineering behavior and testable scenarios;
+- decisions: resolved work-item decision/basis;
+- ADR: only a meaningful cross-cutting architecture decision.
+
+Pause reconciliation when an answer would materially change higher-level approved scope, contradict another authority/ADR, or require a new cross-cutting decision. Continue read-only grilling when appropriate.
+
+## 4. Boundaries
+
+Do not:
+- implement production code;
+- invoke subagents;
+- create artifacts merely because grilling occurred;
+- infer approval from an answer;
+- silently write local or external authorities without the applicable session/write authorization.
+
+Stop when:
+- the human says stop/done/pause;
+- no material issues remain;
+- a true scope/decision/action gate appears;
 - the human switches workflow.
 
-## Natural completion
+## 5. Natural completion
 
 Summarize once:
-- decisions strengthened,
-- unresolved issues,
+- decisions strengthened;
+- documents or proposed external updates changed, if any;
+- unresolved issues/conflicts;
 - recommended next workflow.
 
 Typical next workflows:
-- `/grill-with-docs` to reconcile resolved decisions,
-- `/refine-requirements` for systematic detailed coverage,
-- `/start-work` when the item is ready.
+- `/refine-requirements` for systematic detailed coverage;
+- `/start-work` when the item is ready;
+- normal review/approval when a material requirement gate remains.