@ogygie/core 0.16.0 → 0.18.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ogygie/core",
-  "version": "0.16.0",
+  "version": "0.18.0",
   "description": "Ogygie framework core: manifest/spec/error schemas, generic tenancy and gate tooling. Ships TypeScript sources — Ogygie products run tsx/vitest by construction (D1).",
   "license": "MIT",
   "type": "module",

package/src/manifest-owners.test.ts

@@ -265,8 +265,12 @@ describe("hasImplementation — ce qui prouve qu'une spec draft a déjà du code
     }
   });
 
-  it("une FEATURE skeleton dont le dossier existe a bien du code — c'est la preuve historique", () => {
-    expect(hasImplementation(owner("feature", "skeleton"), true)).toBe(true);
+  it("une FEATURE skeleton dont le dossier existe n'a PAS de code déclaré — la branche spéculative de D26 porte un dossier avant la signature", () => {
+    // La preuve historique (« un dossier de feature naît avec son code ») est
+    // retirée : le générateur émet un dossier pendant que la spec attend sa
+    // validation, et le gate refusait l'état que le processus prescrit
+    // (FAILURES.md 2026-10-18). Le statut déclaré est la seule preuve.
+    expect(hasImplementation(owner("feature", "skeleton"), true)).toBe(false);
     expect(hasImplementation(owner("feature", "skeleton"), false)).toBe(false);
   });
 
@@ -277,4 +281,9 @@ describe("hasImplementation — ce qui prouve qu'une spec draft a déjà du code
     expect(hasImplementation(owner("package", "skeleton"), true)).toBe(false);
     expect(hasImplementation(owner("framework-package", "skeleton"), true)).toBe(false);
   });
+
+  it("MUTATION : une entrée in-progress ou delivered dont la spec reste draft est le défaut que le gate attrape encore", () => {
+    expect(hasImplementation(owner("feature", "in-progress"), false)).toBe(true);
+    expect(hasImplementation(owner("feature", "delivered"), true)).toBe(true);
+  });
 });

package/src/manifest-owners.ts

@@ -162,22 +162,24 @@ export function findSpecOwner(
  * Does an implementation of this spec exist? The question the `draft` rule of
  * the spec lifecycle rests on ("draft = no code yet").
  *
- * A declared status above `skeleton` always answers yes. A FOLDER on disk only
- * answers yes for a FEATURE, whose folder is born with its code and is
- * therefore evidence of it. A package's folder is NOT evidence: the manifest
- * gate REQUIRES it to exist (MANIFEST_PACKAGE_NOT_FOUND), so a package
- * declared `skeleton` whose spec is still `draft` could satisfy neither gate —
- * one demands the folder, the other reads it as code, and the project is stuck
- * between two governed files it may not edit. Observed on a consumer project
- * the day it declared its first package before writing it.
+ * The answer is the STATUS the map declares, and nothing else: an entry above
+ * `skeleton` claims code, a `skeleton` entry claims none — it is a proposal on
+ * the map. A folder on disk is NOT evidence. For a package it never was: the
+ * manifest gate REQUIRES the folder (MANIFEST_PACKAGE_NOT_FOUND), so reading it
+ * as code left a project stuck between two governed files. For a feature it
+ * used to be — a feature's folder was born with its code — until speculative
+ * execution (DECISIONS.md D26 of the framework repo): a generated feature has
+ * its folder on its branch while its spec is still `draft`, awaiting the human
+ * signature, and the gate refused the very state the process prescribes
+ * (framework FAILURES.md 2026-10-18). The status is what the author declares;
+ * the folder is what a generator or a session left there.
  *
  * Lives here rather than in the gate script for the reason the whole module
  * exists: the rule travels with the versioned package, not with a copy each
  * project keeps.
  */
-export function hasImplementation(owner: SpecOwner, folderExists: boolean): boolean {
-  if (owner.status !== "skeleton") return true;
-  return owner.kind === "feature" && folderExists;
+export function hasImplementation(owner: SpecOwner, _folderExists: boolean): boolean {
+  return owner.status !== "skeleton";
 }
 
 /** What a refusal should suggest — both natures, never one that cannot exist. */