Regenerate forms from the form-grammar engine (one question, one door rule)

'What is it?' replaces 'Type tag'; the door rule opens every form;
Software application off the data form's dropdown (it's a reference —
add via 'Add a contextual entity'); contextual intro updated.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: dansand

.github/ISSUE_TEMPLATE/add-contextual-entity.yml

@@ -6,11 +6,15 @@ labels:
 body:
 - type: markdown
   attributes:
-    value: Add a **remote** thing this dataset points to (a *contextual entity*) —
-      a person, a publication, the software you used, a funder, or large data hosted
-      elsewhere — by its identifier (DOI / ORCID / ROR / URL). An action mints it
-      in the crate, links it to the dataset, and `enrich` fills in the details. *(Local
-      things — files/folders — are data entities; use the other forms for those.)*
+    value: 'Add a thing this dataset points to (a *contextual entity*) — a person,
+      a publication, the software you used, a funder, or large data hosted elsewhere
+      — by its identifier (DOI / ORCID / ROR / URL). An action mints it in the crate,
+      links it to the dataset, and `enrich` fills in the details.
+
+
+      > **Where is it?** *In this repository* → it''s a **data entity** (use *Edit
+      a data entity*, or its typed forms). *Hosted elsewhere* → it''s a **reference**
+      (use *Add a contextual entity*).'
 - type: dropdown
   id: ctx_kind
   attributes:

.github/ISSUE_TEMPLATE/configure-crate.yml

@@ -6,11 +6,16 @@ labels:
 body:
 - type: markdown
   attributes:
-    value: Configure the dataset as a whole — title, description, license, creators.
-      *(You can leave the issue title above as-is — it's just a marker; the dataset's
-      title is the field below.)* On submit, an action writes these onto the crate's
+    value: 'Configure the dataset as a whole — title, description, license, creators.
+      *(You can leave the issue title above as-is — it''s just a marker; the dataset''s
+      title is the field below.)* On submit, an action writes these onto the crate''s
       **root** entity (`ro-crate-metadata.json`, the single source of truth). **Edit
       the crate afterwards (CLI / Crate-O), not by reopening this issue.**
+
+
+      > **Where is it?** *In this repository* → it''s a **data entity** (use *Edit
+      a data entity*, or its typed forms). *Hosted elsewhere* → it''s a **reference**
+      (use *Add a contextual entity*).'
 - type: input
   id: title
   attributes:

.github/ISSUE_TEMPLATE/edit-data-entity.yml

@@ -6,10 +6,16 @@ labels:
 body:
 - type: markdown
   attributes:
-    value: Edit metadata for one **local file or folder** in this dataset (a *data
+    value: 'Edit metadata for one **local file or folder** in this dataset (a *data
       entity*). Pick it above, then fill only what you want to set (blank = leave
-      as-is). On submit, an action writes it into the crate. Type-specific fields
-      and richer editing live in **Crate-O**.
+      as-is). On submit, an action writes it into the crate. Picking a type under
+      *What is it?* unlocks that type''s fields on a dedicated form after the next
+      build.
+
+
+      > **Where is it?** *In this repository* → it''s a **data entity** (use *Edit
+      a data entity*, or its typed forms). *Hosted elsewhere* → it''s a **reference**
+      (use *Add a contextual entity*).'
 - type: dropdown
   id: path
   attributes:
@@ -21,15 +27,14 @@ body:
 - type: dropdown
   id: entity_type
   attributes:
-    label: Type tag
-    description: Optional. *Source code* = your own code/scripts in this repo. *Application*
-      = a packaged tool/solver you used (often better added via 'Add a reference').
-      Picking a type unlocks its type-specific fields on a dedicated form.
+    label: What is it?
+    description: Optional — what this file/folder IS. Picking a type unlocks its type-specific
+      fields on a dedicated form after the next build. (A packaged tool you merely
+      *used* lives elsewhere → add it via *Add a contextual entity*.)
     options:
     - (keep current)
     - Dataset
     - Software source code (your code / scripts in this repo)
-    - Software application (a packaged tool / solver you used)
     - Image / figure
     - Other (generic creative work)
   validations:

.github/ISSUE_TEMPLATE/tag-website-content.yml

@@ -6,11 +6,16 @@ labels:
 body:
 - type: markdown
   attributes:
-    value: Tag a **local file** with the role it plays on this record's web page —
-      its *communicative function* (graphical abstract, setup diagram, figure…). Pick
-      the file and its role; an action records the role on the crate (as `additionalType`,
-      keeping the file's structural type) and stores your caption. The role decides
+    value: 'Tag a **local file** with the role it plays on this record''s web page
+      — its *communicative function* (graphical abstract, setup diagram, figure…).
+      Pick the file and its role; an action records the role on the crate (as `additionalType`,
+      keeping the file''s structural type) and stores your caption. The role decides
       where the asset appears on the page.
+
+
+      > **Where is it?** *In this repository* → it''s a **data entity** (use *Edit
+      a data entity*, or its typed forms). *Hosted elsewhere* → it''s a **reference**
+      (use *Add a contextual entity*).'
 - type: dropdown
   id: path
   attributes: