Architecture decisions: files, diagram references, views and panels

- *.archify-decision files: id (unique, words), title, status, date,
  elements, diagrams, supersedes, and prose; parsed, merged and link-checked
  in the model index; diagnostics on the file
- diagrams point at decisions with decisions: [...] on the diagram, nodes
  and edges; stripped before Archify, unknown ids reported, completion,
  hover and go-to-definition for the ids and for elements/diagrams/
  supersedes in decision files
- Decisions panel on the main.archify page; Decisions rail panel under a
  diagram (hover lights up the node or connection); decisions on element
  cards and in the element dialog; decision view for the file, with a
  lost-model note outside a model
- Archify | New Decision… command and template; editor schemas; the three
  New Model examples carry decisions; docs, changelog, 0.8.0

examples/online-shop/0200-containers/online-shop.archify

@@ -3,6 +3,7 @@ diagram_type: architecture
 meta:
   title: Containers
   output: containers.html
+decisions: [postgres-as-source-of-truth]
 components:
   - ref: customer
     pos: [40, 160]
@@ -22,6 +23,7 @@ components:
   - ref: queue
     pos: [460, 360]
     size: [130, 60]
+    decisions: [queue-between-api-and-worker]
   - ref: worker
     pos: [670, 460]
     size: [130, 60]
@@ -34,6 +36,6 @@ connections:
   - { from: web, to: api, label: JSON }
   - { from: api, to: cache, label: read }
   - { from: api, to: db, label: SQL }
-  - { from: api, to: queue, label: enqueue, labelAt: [560, 290] }
+  - { from: api, to: queue, label: enqueue, labelAt: [560, 290], decisions: [queue-between-api-and-worker] }
   - { from: queue, to: worker, label: poll }
   - { from: worker, to: db, label: SQL, labelAt: [735, 420] }