…on, and complexity comparison

- GitHub provider updateTicket now fetches existing issue before PATCH to
  merge metadata (classifications, references, relationships) instead of
  overwriting them. addRelationship/addReference previously wiped all
  existing metadata.
- createTicket returns the result of updateTicket when closing on create,
  so the returned ticket reflects the correct status.
- serializeTicket excludes body from YAML frontmatter since it is already
  stored as markdown content after the closing ---.
- matchesQuery uses ordinal complexity ranking instead of lexicographic
  string comparison (e.g., "medium" > "high" was incorrectly true).
- Added unit tests for body round-trip, complexity filtering, and GitHub
  metadata serialization/merge.

https://claude.ai/code/session_0129tj2WT2v7pjiktvWx2WFR

https://claude.ai/code/session_0129tj2WT2v7pjiktvWx2WFR

TypeScript fixes:
- send.components.test.ts: restore Parameters<> typing on loadConfig spread
  to fix TS2556 (unknown[] spread is not a tuple type)
- gateway e2e test: add explicit 'return undefined' in mock implementations
  so they resolve Promise<undefined> rather than Promise<void>, which is
  not assignable to Promise<ReplyPayload | ReplyPayload[] | undefined>

issue-tracking improvements:
1. Status fidelity (GitHub provider): persist the granular OpenClaw status
   (backlog/ready/in_progress/blocked/in_review/done/canceled) inside the
   openclaw-issue-meta comment so it survives round-trips through GitHub,
   rather than collapsing to the coarse open/closed mapping on every read
2. queryDag caps: local provider caps at 10 000 tickets; GitHub provider
   caps at 500 and also fixes per_page being clamped to the GitHub API
   maximum of 100 (previously Number.MAX_SAFE_INTEGER caused a 422 error)
3. Duplicate relationship prevention: both providers now deduplicate by
   (kind, ticketId) when appending relationships so calling addRelationship
   twice with the same edge is idempotent
4. Injectable lock strategy: extract TicketLockStrategy interface and
   FileTicketLockStrategy class so callers can supply an alternative
   (e.g. Redis SET NX, network advisory lock) for multi-machine deployments
5. New agent tools: issue_tracking_get and issue_tracking_update expose
   single-ticket fetch and field-level updates to agents; previously only
   create/query/link/dag were available

https://claude.ai/code/session_0129tj2WT2v7pjiktvWx2WFR

Claude/review codex code i nz nh