Agent: make the issue→PR orchestrator repo-independent and de-branded (#63)

[MateuszPaulski]

Makes the airside-agent issue→PR orchestrator repo-independent and adds the owner-requested process capabilities, per the approved spec (v3) on the issue. All changes live under .claude/ + docs/ — no product source, no changeset.

• Config-sourced repo/owner — SKILL.md §Config is the single source of REPO/OWNER/PICKUP_LABEL/BRANCH_PREFIX/REVIEW_CAP; every call site now uses placeholder forms (--repo <REPO>, <BRANCH_PREFIX><n>), the GraphQL -F o=…/-F r=… split is derived from REPO, and all six .claude/agents/airside-*.md read REPO/BRANCH from their spawn inputs instead of literals.
• Recipe extraction — the whole gh/graphql/jq command surface moves verbatim into .claude/skills/airside-agent/references/github.md, keyed by op name (plus new mergeable-check and create-issue recipes); the runbook keeps the algorithm and links each op to its recipe.
• Provider seam (design only) — references/providers.md names the abstract operations (listActionableTasks, createTask, readMergeability, …) with GitHub as the one implementation; Jira later.
• Merge-conflict PRs are actionable — reconcile reads mergeability (UNKNOWN = retry next tick, never conflicting); CONFLICTING triggers a priority conflicts op → fixer MODE: conflicts (merge-not-rebase, no force-push, lint+tests, Airside-Agent-Conflicts: true trailer as the one-attempt guard; semantic conflicts escalate to blocked + owner note).
• Filing mode — /airside-agent file <description> files one issue inline (no subagent — the interview needs the top-level invocation), per filing-github-issues; the agent label only on explicit owner opt-in.
• Read-side script — scripts/tick-scan.sh <REPO> consolidates the per-tick read fan-out into one JSON (verified live: parity with the individual recipes on the current 4 agent issues). Writes stay individual recipes (commit-last ordering is the crash-recovery design).
• Legacy cleanup — the retired docs/ideas.md/docs/issues.md mentions are dropped from triage/spec-author/builder.
• ADR — recorded as ADR-0050 (the spec named ADR-0044, but 0044–0047 were taken by other work since the spec was written; at merge time main had landed ADR-0049 and PR Widget: page-level / unanchored comments (start a thread without a pin) #70 claims 0048, so 0050 is the next free number per the newest-last rule). Includes the deferred air-agent rename decision.
• Follow-up filed — Agent: rename the orchestrator to the neutral air-agent namespace #72 (the de-brand rename, owner-coordinated cutover).

Verified: grep gate clean (no Airnauts/airside literal outside §Config / "e.g." text), moved recipe blocks diff-checked against the pre-extraction snippets, tick-scan.sh run live with recipe-parity spot checks, pnpm lint green. The hand-run tick happens post-merge per the spec's Testing section.

Closes #63

🤖 Draft opened by airside-agent — automated build of #63.

[MateuszPaulski]

🤖 airside-agent review — b0776be · 4 finding(s)

Sev	Location	Finding
🟠 high	docs/adr.md:1669	ADR-0048 collides with PR #70's claimed number; adr.md conflicts with main — renumber to ADR-0050 during conflict resolution
🟡 medium	scripts/tick-scan.sh:33	gh api --paginate --jq '[...]' emits one array per page — breaks --argjson past 100 comments
🟡 medium	SKILL.md:299	One-attempt conflicts guard mis-fires on a new conflict against an unchanged head
⚪ low	scripts/tick-scan.sh:39	Branch probe deviates from the recipe (https URL vs origin), assumes git credentials

Extraction verified faithful (recipes byte-identical, grep gate clean, tick-scan.sh ran green live). The high (merge main + renumber ADR) is being auto-fixed.

[MateuszPaulski]

🤖 airside-agent review — 2c5bf3a · 1 finding(s)

Sev	Location	Finding
⚪ low	packages/client/src/panel/PanelListView.tsx:7	Merge resolution touches product source (one-line biome-canonical import reorder) despite "docs/tooling only" claim

Prior high (ADR-0050 renumber + main merge) and both mediums (tick-scan.sh pagination, conflicts-guard prose) verified resolved. No highs — CI-gate then promote to ready next round.