@bakers-build/core 0.1.1 → 0.1.2-next.133

package/dist/src/workflow/step-contract.d.ts

@@ -1,5 +1,5 @@
 /** The workflow states an agent works — the legal `step` values. */
-export declare const WORKFLOW_STEPS: readonly ["qualification", "spec", "diagnose", "coding", "review", "pre_deployment", "post_deployment", "verifying", "summary"];
+export declare const WORKFLOW_STEPS: readonly ["qualification", "plan", "working", "spec", "diagnose", "coding", "review", "pre_deployment", "post_deployment", "verifying", "summary"];
 export type WorkflowStep = (typeof WORKFLOW_STEPS)[number];
 /**
  * The machine-readable classification of a contract defect, for consumers that
@@ -85,7 +85,7 @@ export interface SkillContract {
 }
 /**
  * A concrete `(work_type, workflow, step)` the project can produce. `work_type`
- * is `null` for a non-work-typed step (qualification, spec, deployment,
+ * is `null` for a non-work-typed step (qualification, plan, deployment,
  * verification), a `work:*` label (without the prefix) otherwise.
  */
 export interface Triple {
@@ -161,10 +161,10 @@ export declare const WORKFLOW_CLAIMABLE_STATES: Record<string, readonly Workflow
  *
  * A **work type** exists for the project because some loaded **owner** declares it;
  * its participating steps are the union of `when.step` across every owner declaring
- * it. Those steps are then crossed against **all five** workflows — not merely the
+ * it. Those steps are then crossed against **every** workflow — not merely the
  * ones the declaring skill happens to list — because that is what makes a coverage
  * gap real rather than tautological: a project that can route `work:code` at
- * `coding` must be able to route it at `coding` in every workflow that claims there.
+ * `working` must be able to route it at `working` in every workflow that claims there.
  *
  * A step no work type participates in carries a `null` work type (qualification,
  * the deployment and verification steps). An owner whose `when.work_type` is `*` or
@@ -175,8 +175,8 @@ export declare const WORKFLOW_CLAIMABLE_STATES: Record<string, readonly Workflow
  * project.** Because a work type exists here only if some loaded owner declares it,
  * deleting the last owner of a work type does not open a coverage gap — it shrinks
  * the triple set, and the validation stays green. Removing `- @bakers-build/docs-authoring`
- * from this repository's own `WORKFLOW.md` yields `9 → 8` owners and `24 → 16`
- * triples, all covered, although every `work:docs` ticket would then reach `coding`
+ * from this repository's own `WORKFLOW.md` drops one owner and its triples, all
+ * still covered, although every `work:docs` ticket would then reach `working`
  * with no owner at all. The set of work types a project's tickets can actually
  * carry lives in the ticket store's `work:*` vocabulary, which this function cannot
  * see; closing the gap means feeding that vocabulary in, which is its own change.

package/dist/src/workflow/step-contract.js

@@ -21,6 +21,9 @@ import { parse as parseYaml } from 'yaml';
 /** The workflow states an agent works — the legal `step` values. */
 export const WORKFLOW_STEPS = [
     'qualification',
+    'plan',
+    'working',
+    // shortcut: spec/diagnose/coding stay until the skills move to plan/working, then remove them.
     'spec',
     'diagnose',
     'coding',
@@ -423,9 +426,7 @@ function tripleLabel(triple) {
  * filesystem and no Drupal access. A workflow added there must be added here too.
  */
 export const WORKFLOW_CLAIMABLE_STATES = {
-    bb_feature: ['qualification', 'spec', 'coding', 'review'],
-    bb_bug: ['qualification', 'diagnose', 'coding', 'review'],
-    bb_chore: ['qualification', 'spec', 'coding', 'review'],
+    bb_work: ['qualification', 'plan', 'working', 'review'],
     bb_deployment: ['pre_deployment', 'post_deployment'],
     bb_verification: ['verifying', 'summary'],
 };
@@ -437,10 +438,10 @@ export const WORKFLOW_CLAIMABLE_STATES = {
  *
  * A **work type** exists for the project because some loaded **owner** declares it;
  * its participating steps are the union of `when.step` across every owner declaring
- * it. Those steps are then crossed against **all five** workflows — not merely the
+ * it. Those steps are then crossed against **every** workflow — not merely the
  * ones the declaring skill happens to list — because that is what makes a coverage
  * gap real rather than tautological: a project that can route `work:code` at
- * `coding` must be able to route it at `coding` in every workflow that claims there.
+ * `working` must be able to route it at `working` in every workflow that claims there.
  *
  * A step no work type participates in carries a `null` work type (qualification,
  * the deployment and verification steps). An owner whose `when.work_type` is `*` or
@@ -451,8 +452,8 @@ export const WORKFLOW_CLAIMABLE_STATES = {
  * project.** Because a work type exists here only if some loaded owner declares it,
  * deleting the last owner of a work type does not open a coverage gap — it shrinks
  * the triple set, and the validation stays green. Removing `- @bakers-build/docs-authoring`
- * from this repository's own `WORKFLOW.md` yields `9 → 8` owners and `24 → 16`
- * triples, all covered, although every `work:docs` ticket would then reach `coding`
+ * from this repository's own `WORKFLOW.md` drops one owner and its triples, all
+ * still covered, although every `work:docs` ticket would then reach `working`
  * with no owner at all. The set of work types a project's tickets can actually
  * carry lives in the ticket store's `work:*` vocabulary, which this function cannot
  * see; closing the gap means feeding that vocabulary in, which is its own change.
@@ -543,7 +544,7 @@ export function expandLoad(workflowMd, byName) {
     // BB-436: a `## Loaded skills` section that yields no load site at all is its
     // own defect and needs its own message. Expanding it into an empty skill set
     // let the failure surface much later as `no skill matches triple (—,
-    // bb_feature, qualification) — coverage gap`, which sends the author looking
+    // bb_work, qualification) — coverage gap`, which sends the author looking
     // for a missing work-type skill when the real cause is almost always that their
     // list is indented — the one shape the indent-0 anchor turns into nothing.
     //

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bakers-build/core",
-  "version": "0.1.1",
+  "version": "0.1.2-next.133",
   "description": "bakers.build surface-agnostic kernel: host contract, split-config helpers, addon preset/discovery machinery, shared primitives.",
   "type": "module",
   "license": "MIT",