feat(protocol): self-documenting schema and directive grammar

[c-ferrier]

Transforms Lore from a static convention into a runtime-discoverable knowledge protocol. By formalizing Core and Custom trailer definitions with types, patterns, and operational directives, the CLI now acts as a schema registry for both humans and AI agents.

Key Architectural Shifts:

1. Discovery Engine: New lore config command exposes the full protocol schema.
2. Trigger-Action Grammar: Formalized [trigger:parameter] directives for operational rules.
3. Validation Engine: Custom trailers now separate cardinality (multivalue) from content validation (options, pattern), enabling complex types like multi-value enums.
4. Flexible Governance: Introduced permissive mode for hybrid schema enforcement.

Usage Examples (.lore/config.toml)

1. Multi-Value Enum (Select many from list)

Allows selecting multiple values from a fixed list.

  [trailers.definitions.Platforms]
  description = "Target operating systems"
  multivalue = true
  validation = "options"
  options = ["Linux", "macOS", "Windows", "Android", "iOS"]

2. Standardizing Attribution (Co-authored-by)

Enforce Git-standard formatting and provide automated squash instructions.

[trailers.definitions.Co-authored-by]
  description = "Git standard co-author attribution"
  multivalue = true
  validation = "pattern"
  pattern = "^.+ <.+@.+>$"
  directives = [
    "[on:squash] Identify all unique intermediate authors in the range",
    "[on:squash] Add authors (excluding the final committer) to this trailer"
  ]

3. Mandatory Unique IDs (Ticket-Id)

[trailers.definitions.Ticket-Id]
  description = "JIRA or Linear ticket identifier"
  multivalue = false
  validation = "pattern"
  pattern = "^PROJ-[0-9]+$"
  required = true

4. Team-Specific Rules

 [trailers.definitions.Department]
  description = "The department responsible for this change"
  multivalue = false
  validation = "options"
  options = ["Engineering", "Product", "Design", "Security"]
  required = true

🔍 Self-Documenting Core Protocol

The native Lore Protocol trailers (Lore-id, Confidence, etc.) now use this same orthogonal model and are discoverable via lore config --core.

Example of what an agent sees for Lore-id:

Lore-id:
    Description: Unique identifier for this knowledge atom
    Type:        string
    Pattern:     ^[0-9a-f]{8}$
    Required:    true
    Directives:
       - [on:amend] Preserve the existing ID to maintain graph integrity
       - [on:commit] Handled by Lore CLI; MUST NOT manually generate IDs or use git hashes
       - [on:commit] The CLI automatically assigns a random 8-character hex string