feat: participation and RACI labels, written on the project page (#118)

Files changed:
- CHANGES.md
- VERSION
- instructions/gtd-weekly-review/SKILL.md
- instructions/link-taxonomy.md
- kb/entities/COLLECTION.md
- kb/gtd/COLLECTION.md
- types/project.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

kb/entities/COLLECTION.md

@@ -1,7 +1,7 @@
 ---
 profile: entities
 outbound:
-  entities: [depends-on, required-by, runs-on, hosts, uses, produces, consumes, maintains, owns, authored, alternative-to, implements, part-of, composition, supersedes, derived-from, adapted-from, see-also]
+  entities: [depends-on, required-by, runs-on, hosts, uses, produces, consumes, maintains, owns, owned-by, authored, involves, alternative-to, implements, part-of, composition, supersedes, derived-from, adapted-from, see-also]
   concepts: [implements, exemplifies, rests-on, applies-when, operates-on, invokes, authored, alternative-to, see-also]
   sources: [evidenced-by, defined-in, see-also]
   comparisons: [compares-with, see-also]
@@ -66,6 +66,13 @@ mirrored clique grows fastest. `derived-from` and `adapted-from` are here for th
 re-implementation - one tool worked up out of another - which is a lineage claim the operational
 labels cannot make.
 
+`involves` and `owned-by` are the participation labels, and they run the other way from
+`authored`/`owns`/`maintains`: written on the codebase or system, pointing at the person or
+organization - `[Codebase] involves [Person]`. `involves` is the contributor who neither answers
+for the thing nor keeps it running; take `maintains` or `owns` from the person's side when one of
+those is true instead. `owned-by` is `owns` read from the thing's side - write whichever page a
+reader would ask the question on, not both by reflex.
+
 Adding a label here is a deliberate contract change, not a way around a refusal.
 
 ## Outbound linking