Canonize work-record flavor and residual default-exclusion.

STATE-WP-0092-T01: flavor is a closed bucket on workplans and tasks;
residuals are a flavor, not a kind, and are omitted from default open
views until demand or risk promotes them. depends_on is the workplan
frontmatter edge.

canon/standards/workplan-terminology-fleet_v0.1.md

@@ -4,19 +4,20 @@ type: standard
 title: "Workplan Terminology (Fleet) v0.1"
 domain: custodian
 status: accepted
-version: "0.2"
+version: "0.3"
 owner: the-custodian
-revision: "accepted-1"
-last_reviewed: "2026-08-31"
+revision: "accepted-2"
+last_reviewed: "2026-09-14"
 review_interval: 6m
 created: "2026-07-08"
-updated: "2026-07-20"
+updated: "2026-09-14"
 scope: fleet
 related_workplans:
   - CUST-WP-0055
   - STATE-WP-0054
   - STATE-WP-0069
   - CUST-WP-0060
+  - STATE-WP-0092
 supersedes: none
 ---
 
@@ -63,6 +64,19 @@ intake kind (state-hub suggestions table: read-only legacy pending
 close-out). This file keeps its `_v0.1` name for reference stability; the
 frontmatter `version` field is authoritative.
 
+## Flavor and depends_on (v0.3 addendum, STATE-WP-0092)
+
+Workplans and tasks may carry **flavor**: `planning`, `implementation`,
+`refactoring`, `extension`, or `residual`. Flavor is a bucket, not a kind
+and not a status. `residual` leftovers are live records but are **not**
+equal to main functional/non-functional demand. Default State Hub open
+views omit them until demand or risk promotes the flavor.
+
+Workplan frontmatter `depends_on` is the canonical list of blocker
+workplan ids. Prefer that spelling over `depends_on_workplans`.
+
+Normative detail: `work-record-types_v0.1.md` § Flavor.
+
 Use **workplan** in human-facing prose: `SCOPE.md`, `AGENTS.md`, `INTENT.md`,
 README, workplan bodies, operator runbooks, and agent session guidance.