plain-forge 1.0.14 → 1.0.15

package/forge/rules/func-specs.md

@@ -74,6 +74,5 @@ When writing or editing a `***functional specs***` section in a `.plain` file, a
   - All :Participant: members of the :Conversation: can see the new :Message:.
 
   ***acceptance tests***
-  - Sending a :Message: to a :Conversation: with three participants should
-    make the message visible to all three.
+  - Sending a :Message: to a :Conversation: with three participants should make the message visible to all three.
 ```

package/forge/rules/linked-resources.md

@@ -14,8 +14,8 @@ A linked resource **must not** be any of the following:
 1. **A folder / directory.** `[integrations](src/integrations/)`, `[host project](../host_project/)` are invalid — the renderer cannot ingest a directory. Pick the single most representative file inside (a `README.md`, an exemplar source file, a manifest) and link **that**.
 2. **A URL / external location.** `[Stripe docs](https://stripe.com/docs/api)`, any `http://` / `https://` / `ftp://` / `git://` / `s3://` / `gs://` target. Linked resources are local-file only. If a URL's content is essential, fetch it once, save the response to a text file under `resources/`, and link the saved file.
 3. **A binary file.** PNG, JPG, GIF, PDF, DOCX, XLSX, ZIP, MP3, MP4, compiled binaries (`.exe`, `.so`, `.class`, `.wasm`), and anything else that isn't human-readable text in its raw form. Binary content cannot be meaningfully consumed by the renderer — transcribe it into a text-based form first (a UI screenshot becomes a Markdown description, a PDF spec becomes a Markdown extract or the underlying JSON Schema / OpenAPI, an architecture diagram becomes a Mermaid block).
+4. **Another `.plain` file.** `[Auth Module](auth.plain)` is invalid. To reference another module, use the `require` or `import` frontmatter directives. Do not link it as a markdown resource; the `plain-dry-run` will flag this as a syntax error.
 
-If the markdown-link target ends with `/`, contains `://`, resolves to a directory, or has a binary extension, **stop** — it cannot be a linked resource. Convert it first.
 
 ## URLs and folder paths must not appear *anywhere* in `.plain` content
 - The constraint is not only about markdown links — URLs and folder paths must not appear **anywhere** in `.plain` content (concept body prose, functional-spec text, implementation reqs, test reqs)
@@ -31,15 +31,15 @@ If the markdown-link target ends with `/`, contains `://`, resolves to a directo
 ```plain
 ***definitions***
 
-- :TaskCreateRequest: is the JSON payload for creating a task, defined by
-  [resources/task_create_request.schema.json](resources/task_create_request.schema.json).
-- :TasksAPI: is the public HTTP surface for tasks, defined by
-  [resources/tasks_openapi.yaml](resources/tasks_openapi.yaml).
+- :TaskCreateRequest: is the JSON payload for creating a task.
+  - It is defined by [resources/task_create_request.schema.json](resources/task_create_request.schema.json).
+- :TasksAPI: is the public HTTP surface for tasks.
+  - It is defined by [resources/tasks_openapi.yaml](resources/tasks_openapi.yaml).
 
 ***functional specs***
 
-- :User: should be able to add :Task: by POSTing :TaskCreateRequest: to the
-  `POST /tasks` endpoint of :TasksAPI:. The endpoint responds per :TasksAPI:.
+- :User: should be able to add :Task: by POSTing :TaskCreateRequest: to the `POST /tasks` endpoint of :TasksAPI:.
+  - The endpoint responds per :TasksAPI:.
 ```
 
 ## Each linked resource is referenced from exactly one place
@@ -50,8 +50,8 @@ If the markdown-link target ends with `/`, contains `://`, resolves to a directo
 ```plain
 ***definitions***
 
-- :TaskModalSpec: is the user-interface contract for the task modal,
-  fully described in [task_modal_specification.yaml](task_modal_specification.yaml).
+- :TaskModalSpec: is the user-interface contract for the task modal.
+  - It is fully described in [task_modal_specification.yaml](task_modal_specification.yaml).
 
 ***functional specs***
 

package/forge/skills/add-resource/SKILL.md

@@ -26,17 +26,16 @@ Use standard markdown link syntax inside any spec section:
 
 ```plain
 ***definitions***
-- :AuthData: is the authentication data structure. Its format is defined
-  in the [auth schema](resources/auth_schema.json).
+- :AuthData: is the authentication data structure.
+  - Its format is defined in the [auth schema](resources/auth_schema.json).
 
 ***implementation reqs***
-- When transforming :BackupData:, use the JOLT transform defined in
-  [backup_transform.jolt](resources/backup_transform.jolt).
+- When transforming :BackupData:, use the JOLT transform.
+  - The transform is defined in [backup_transform.jolt](resources/backup_transform.jolt).
 
 ***functional specs***
 
-- The system should expose an API conforming to the
-  [API specification](resources/api_spec.yaml).
+- The system should expose an API conforming to the [API specification](resources/api_spec.yaml).
 ```
 
 ## Path Rules

package/forge/skills/analyze-if-func-spec-too-complex/SKILL.md

@@ -69,10 +69,9 @@ Too complex:
 
 Acceptable (separate the modes):
 - The system should process standard :Order: by validating and storing it.
-- The system should process express :Order: by queuing it for immediate dispatch
-  without validation.
-- The system should process bulk :Order: by splitting it into sub-orders of 100
-  items each and processing them individually.
+- The system should process express :Order: by queuing it for immediate dispatch without validation.
+- The system should process bulk :Order: by splitting it into sub-orders of 100 items each.
+  - Each sub-order is processed individually.
 ```
 
 ### 4. Cross-Cutting Concerns
@@ -88,8 +87,7 @@ Too complex:
 Acceptable (separate concerns):
 - The system should fetch :Resource: items from the external API.
 - The system should paginate when fetching :Resource: items from the external API.
-- The system should retry fetching :Resource: on transient errors using
-  exponential backoff.
+- The system should retry fetching :Resource: on transient errors using exponential backoff.
 ```
 
 ### 5. UI Complexity

package/forge/skills/break-down-func-spec/SKILL.md

@@ -111,10 +111,10 @@ If the spec describes different modes or branches, give each its own spec.
 **After:**
 ```plain
 - The system should generate a standard :MealPlan: using round-robin :Recipe: assignment.
-- The system should generate a restrictive :MealPlan: by filtering out excluded
-  :Ingredient: items before applying round-robin assignment.
-- The system should allow :User: to manually assign :Recipe: items to individual
-  :Slot: items for a custom :MealPlan:.
+- The system should generate a restrictive :MealPlan:.
+  - Excluded :Ingredient: items are filtered out first.
+  - Round-robin :Recipe: assignment is then applied.
+- The system should allow :User: to manually assign :Recipe: items to :Slot: items for a custom :MealPlan:.
 ```
 
 ### Strategy 5: Build UI Incrementally

package/forge/skills/load-plain-reference/SKILL.md

@@ -184,8 +184,8 @@ The frontmatter is enclosed between `---` markers and supports:
 Specifications can reference external files using markdown link syntax. The linked resource is passed along with the spec to the renderer. File paths are resolved relative to the `.plain` file location. Only files in the same folder (and subfolders) are supported.
 
 ```plain
-- :User: should be able to add :Task:. The details of the user interface
-  are provided in the file [task_modal_specification.yaml](task_modal_specification.yaml).
+- :User: should be able to add :Task:.
+  - The user-interface details are in [task_modal_specification.yaml](task_modal_specification.yaml).
 ```
 
 #### Hard constraint: a linked resource is always a single, text-based file on disk
@@ -220,15 +220,15 @@ The accompanying spec line should describe the *role* of the artifact ("the requ
 ```plain
 ***definitions***
 
-- :TaskCreateRequest: is the JSON payload for creating a task, defined by
-  [resources/task_create_request.schema.json](resources/task_create_request.schema.json).
-- :TasksAPI: is the public HTTP surface for tasks, defined by
-  [resources/tasks_openapi.yaml](resources/tasks_openapi.yaml).
+- :TaskCreateRequest: is the JSON payload for creating a task.
+  - It is defined by [resources/task_create_request.schema.json](resources/task_create_request.schema.json).
+- :TasksAPI: is the public HTTP surface for tasks.
+  - It is defined by [resources/tasks_openapi.yaml](resources/tasks_openapi.yaml).
 
 ***functional specs***
 
-- :User: should be able to add :Task: by POSTing :TaskCreateRequest: to the
-  `POST /tasks` endpoint of :TasksAPI:. The endpoint responds per :TasksAPI:.
+- :User: should be able to add :Task: by POSTing :TaskCreateRequest: to the `POST /tasks` endpoint of :TasksAPI:.
+  - The endpoint responds per :TasksAPI:.
 ```
 
 **Each linked resource must be referenced from exactly one place** in the project — a single functional spec, implementation requirement, or `***definitions***` entry. Linking the same file from two functional specs (or from a functional spec *and* a requirement, etc.) creates two independent sources of truth: any later edit to one site silently diverges from the other, and the renderer has no way to know which one is canonical.
@@ -243,8 +243,8 @@ For example, instead of linking `task_modal_specification.yaml` from two differe
 ```plain
 ***definitions***
 
-- :TaskModalSpec: is the user-interface contract for the task modal,
-  fully described in [task_modal_specification.yaml](task_modal_specification.yaml).
+- :TaskModalSpec: is the user-interface contract for the task modal.
+  - It is fully described in [task_modal_specification.yaml](task_modal_specification.yaml).
 
 ***functional specs***
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "plain-forge",
-  "version": "1.0.14",
+  "version": "1.0.15",
   "description": "Conversational spec-writing tool for ***plain specification language",
   "type": "module",
   "engines": {