feat(bootstrap): finish FEATURE-WP-0001 State Hub integration workstream

- T01 (Review Generated Integration Files): Reviewed INTENT.md, SCOPE.md, AGENTS.md, .custodian-brief.md. Refined SCOPE.md (removed generic generated placeholder, added repo-specific In/Out Scope, Current State noting completion of WP-0001 and WP-0002, canon alignment). Refined README.md with links to canon-mapping and workplans. Confirmed INTENT and AGENTS already specific.
- T02 (Verify Local Developer Workflow): Confirmed pure-docs repo (no build/test files). Added 'Local Developer Workflow' section to AGENTS.md documenting verification commands (cat/ls for review, hub curls, make fix-consistency from state-hub, progress POSTs) and extension guidance.
- Updated FEATURE-WP-0001 workplan: T01/T02 marked done with detailed notes; frontmatter status set to finished.
- Includes completion of FEATURE-WP-0002 (canon alignment for PRD/UCC, docs/canon-mapping.md + interface card stub, terminology updates with EvaluationScope and ITC mappings).
- Ran make fix-consistency REPO=feature-control after changes (synced hub, set workstreams to finished).

All per AGENTS.md session protocol, workplan instructions, and custodian brief.

Bootstrap workstream now 3/3 complete; no active workstreams remaining.

docs/canon-interface-card.md

@@ -0,0 +1,44 @@
+# feature-control — Canon Interface Card (Stub)
+
+**Status:** draft (per FEATURE-WP-0002 T09)
+**Date:** 2026-06-14
+**Based on:** info-tech-canon/infospace/agent/briefs/consumer-brief.template.md and interface-card.schema.yaml
+
+## Produced Concepts
+- Feature (as ProducerCapability specialization + availability control)
+- FeatureKey
+- EvaluationScope / TargetingScope (EvaluationContext dimension)
+- FeatureDecision (with rich states, reasons)
+- FeatureAvailability / states
+- Feature registry & lifecycle hygiene patterns
+- Multi-signal composition (entitlement + kill + policy + etc.)
+
+## Consumed Concepts (from InfoTechCanon)
+- ITC-ORG: Actor, Agent, Membership, Organization/Unit, Ownership, Tenant patterns
+- ITC-ACCESS: Entitlement, Grant, AuthorizationDecision, Subject/Principal
+- ITC-LAND: Environment, Deployment, Service, Repository, RuntimeResource
+- ITC-GOV: Decision, Control, Evidence, Policy, ProducerCapability, ScopePressure, PurposeFit
+- ITC-TaggingStandard: for feature categories
+- ITC-TASK: for reviews, expiry, stale-flag cleanup, remediation
+
+## Purpose / Consumer Demand
+- Low-impact OpenFeature-based adoption for repos (agentic + human devs)
+- Compute governance and cost control via capability flags
+- Operational safety (kill switches, degraded modes)
+- Agent capability gating (with separate authz)
+- Multi-tenant / multi-vendor / multi-scope availability without hard-coding
+
+## Scope Pressure / Evolution Requests
+- Need for first-class Feature/FeatureAvailability in canon (currently extension candidate)
+- Clarification on EvaluationScope vs producer-scope terminology
+- Interface for feature registry export to repos (GitOps + generated constants)
+- Patterns for multi-signal decision composition
+
+## References
+- docs/canon-mapping.md (primary detailed mapping)
+- workplans/FEATURE-WP-0002-canon-prd-ucc-alignment.md
+- specs/ProductRequirementsDocument.md and UseCaseCatalog.md (canon-aligned)
+- info-tech-canon/infospace/ (models, evaluations, schemas)
+- OpenFeature spec for the repo integration surface
+
+This stub can be expanded into a full consumer brief or validated against canon review-kit once ITC-WP-0011 stabilizes. See FEATURE-WP-0002 T08/T09 for extension proposals.