fix: rename seed files and IDs to match cleaned titles

All 100 seed YAML files now have:
- Filenames that match their id field
- IDs that are slugs of their titles
- No cultural identifiers in titles or IDs

70 files renamed. e.g. quaker-meeting-for-worship.yaml -> meeting-for-worship.yaml,
moroccan-jmaa-village.yaml -> jmaa-village-assembly.yaml,
japanese-hansei.yaml -> hansei-reflection.yaml

seeds/hackerspace-consensus-meeting.yaml

@@ -0,0 +1,44 @@
+id: hackerspace-consensus-meeting
+title: Hackerspace Consensus Meeting
+description: >-
+  A governance meeting format used in many hackerspaces and makerspaces
+  where members propose changes and the group works toward consensus or
+  rough consensus, with an explicit "doctorate" of expertise respected
+  but not privileged. Originating in the global hackerspace movement,
+  with Noisebridge (San Francisco) as a notable exemplar.
+source: Noisebridge / Hackerspace movement
+source_url: https://www.noisebridge.net/
+tags: [hackerspace, consensus, governance, open-source, community]
+forked_from: null
+image: null
+steps:
+  - headline: Post the proposal in advance
+    description: >-
+      The proposer posts the proposal on the hackerspace's wiki or
+      discussion board at least a week before the meeting, so members can
+      read and comment before convening.
+  - headline: Present at meeting
+    description: >-
+      At the meeting the proposer presents the proposal. The facilitator
+      takes clarifying questions, then opens discussion.
+  - headline: Discuss concerns
+    description: >-
+      Members raise concerns, which are listed. The proposer amends or
+      responds. The facilitator ensures those with relevant expertise are
+      heard but not privileged over others.
+  - headline: Test for consensus
+    description: >-
+      The facilitator tests for consensus or rough consensus. A block must
+      be reasoned and accompanied by a willingness to help find a
+      solution.
+  - headline: Record and act
+    description: >-
+      The decision is recorded on the wiki with the date and any
+      stand-asides. Action items are assigned to named members.
+outcome: >-
+  A hackerspace decision is made with members' input, recorded publicly,
+  and acted on by named owners.
+practice: >-
+  Posting in advance is the discipline — decisions made on the spot
+  exclude those not present. A block is a serious act; at Noisebridge it
+  comes with an obligation to work toward resolution.