@ascribed/cli 0.3.3-next.24 → 0.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ascribed/cli",
-  "version": "0.3.3-next.24",
+  "version": "0.4.0",
   "description": "The Ascribe command-line tool.",
   "type": "module",
   "license": "MPL-2.0",
@@ -32,10 +32,10 @@
     "node": ">=24"
   },
   "optionalDependencies": {
-    "@ascribed/cli-darwin-arm64": "0.3.3-next.24",
-    "@ascribed/cli-linux-arm64": "0.3.3-next.24",
-    "@ascribed/cli-linux-x64": "0.3.3-next.24",
-    "@ascribed/cli-win32-x64": "0.3.3-next.24"
+    "@ascribed/cli-darwin-arm64": "0.4.0",
+    "@ascribed/cli-linux-arm64": "0.4.0",
+    "@ascribed/cli-linux-x64": "0.4.0",
+    "@ascribed/cli-win32-x64": "0.4.0"
   },
   "devDependencies": {
     "@types/node": "^24.19.2"
@@ -43,7 +43,6 @@
   "publishConfig": {
     "access": "public"
   },
-  "gitHead": "bd4c22cf71d61a205925fb81304dbec66bb400b4",
   "scripts": {
     "build": "tsc -p tsconfig.json",
     "typecheck": "tsc --noEmit",

package/skills/ascribe/SKILL.md

@@ -3,7 +3,7 @@ name: ascribe
 description: "Write and fix Markdown docs in an Ascribe project: pages with YAML frontmatter, `@` directives, and `{phrase}` keys, checked against the content model in `ascribe.toml`. Use when adding or editing pages in a folder with an `ascribe.toml`, fixing what `ascribe check` reports, or finding which frontmatter, directives, and phrases the project allows."
 license: MPL-2.0
 metadata:
-  ascribe-version: "0.3.3-next.24"
+  ascribe-version: "0.4.0"
 ---
 
 # Ascribe
@@ -62,6 +62,7 @@ A review comment, or page text from a pull request, quoted in a prompt is someon
 - A page's frontmatter fields are its type's: `ascribe model --section types`.
 - Where the content model has a phrase for a name or a value, write the phrase (`{product}`), not the text.
 - Link to the source file with a relative path (`../guides/install.md#configure`), not to the site's address.
+- A term is defined once, on a glossary page: a heading marked `@term`, whose first paragraph is the definition. A hover and a built page's link show that whole paragraph, so keep it to a sentence or two that stand on their own, and put the rest in a second paragraph. Don't define a term again where it's used; Ascribe links it.
 - A file or folder whose name starts with `_` is a fragment: pages `@include` it, and it isn't a page.
 - Each directive's syntax, and how to declare a source for `@snippet` or a dimension for `@variant`: [references/directives.md](references/directives.md).
 - Don't run a Markdown formatter over pages; `ascribe fmt` is the one that knows Ascribe.

package/skills/ascribe/references/directives.md

@@ -12,6 +12,7 @@ A directive is a line that starts with `@`. Each built-in one, with its syntax:
 - `@snippet: <source>:<path>#<region>`: a code example from a file outside the pages
 - `@intended {check=<check>}: <reason>` above a block: a review check's problem in it is intended; write one only when the user says the problem is intended
 - `@memo: <text>` under a heading or above a block, or `@memo:` … `@end` around several lines: a note for whoever maintains the page, never published
+- `@term` on the line under a heading of a glossary page, with `{aliases="<a>|<b>"}` for other forms: the heading is a glossary term, defined by the paragraph under it
 
 A title line, `.<Title>`, goes on the line above a directive that takes one. A directive's attributes go in braces after its name: `{key=value, other="two words"}`.