Super Admin review queue for feature requests and suggested tasks (D544, migration 383)

[guillaumelauzier]

S1: Task for slot S08, after #1103. It is part of #1101.

Do

1. The store, in migration 383. community_tasks holds:
   • id, ticket_id, title, body, audience (a persona or all), status (pending, approved or declined);
   • decided_by, decided_at, decline_reason and created_at.
     A ticket of type task creates a pending row. Leave the ticket form itself alone; Support: a fixed ticket category and an HQ-edited SLA band store (D482, migration 333) #1022 owns the ticket category.
2. The review API, in a new routes/admin_ticket_reviews.ts mounted in index.ts, Super Admin only, with a typed reason and logAdminAction. It lists pending feature requests and suggested tasks, and approves or declines each:
   • Approving a feature adds the feature:approved label to its mirrored issue through services/githubSync.ts. Session 1 then files the build task.
   • Declining adds feature:declined and sends the user the reason.
   • Approving a suggested task publishes it to the community task list (Eadwyn chat: a Task list of approved community tasks (D545) #1108) and grants task_approved through Credits: reward rules and one grant service on the perk credit ledger (D540, migration 381) #1103's grantCredits.
3. The page, after the canvas: an HQ "Review queue" with two tabs, Features and Suggested tasks. Each entry shows its text, who asked (as a link to the account), the priority, the date, and Approve and Decline with a reason.

Owns

• migration 383 and routes/admin_ticket_reviews.ts
• the new HQ review page and its route guard
• tests, and documentation/architecture/decisions/D544.md

Tests

• the Super Admin gate;
• each approve and decline path;
• a task reward granted exactly once;
• the label added on approval.

Mutation-check every assertion.

Design

needs-design. The Claude Design prompt for this page and for #1108 is in the next comment. Build the store and the API now. Build the page once S1 posts that the owner has approved the design.

Numbers

D544, migration 383.

---

Generated by Claude Code

[guillaumelauzier]

S1: The Claude Design prompt for this task and #1108. The owner can paste it into Claude Design. Once the owner approves the design, attach the export here or drop it in design/incoming/; Session 1 then commits it and tells S08 to build the screens.

Design three screens for StudioOS (axal.vc), a venture-studio platform whose AI is called Eadwyn. Match the existing StudioOS look:
- Colours: ground #f4f3f7, ink #18181b, muted #6b6577, hairlines #ececf1, violet #7c3aed (deep #6d28d9, tint #f4f0fe), positive #047857, destructive #b91c1c.
- Type: Space Grotesk for headings, Inter for body text, Roboto Mono for figures.
- Each screen at 1440 wide, plus a phone layout.

Users file support tickets from the Eadwyn chat with a priority (Low, Medium, High, Urgent) and a type (Task, Bug, Feature). Credits are worth US$1 each and are spent on Perks.

1. HQ Review queue (Super Admin only), with two tabs:
   - "Feature requests": each item shows its title, its text, who asked (a link to the account), the priority, the date, and a link to the mirrored GitHub issue.
     - Approve: a short confirmation, after which the request goes to the build queue.
     - Decline: the decliner must type a reason, which the user sees.
   - "Suggested tasks": the same layout, plus an audience picker (all users, or one persona) for Approve. Approving publishes the task to users' Task list and rewards the suggester 10 credits; show that on the button.
   - Counts on each tab, and empty, loading and "Unreadable" states.
2. Eadwyn chat, "Tasks" panel: a tab or drawer next to the conversation.
   - Approved community tasks: title, one line, and a "Start" link.
   - "My suggestions": each one with its state (Pending review, Approved with "+10 credits", or Declined with the reason).
   - A "Suggest a task" button, which opens the existing ticket form with Type = Task.
3. Eadwyn chat, "My tickets" list, showing a bug's bounty state:
   - Under review
   - Confirmed: being fixed
   - Fixed: +150 / +60 / +20 credits
   - Not a bug, with the reason
   - Duplicate, with a link to the original
   Show the user's credit balance with a link to Perks.

Rules:
- Never draw an invented figure. Names are placeholders such as [User name] and [Ticket title].
- A failed read says "Unreadable", never 0.
- Product copy never says advisor, advice, recommendation or fiduciary.

---

Generated by Claude Code

[guillaumelauzier]

STATUS
task: #1107   slot: S08   agent: Claude Code
branch: agent/claude-b/1107-ticket-review-queue (stacked on agent/claude-b/1103-credit-grants: the task reward uses #1111's grantCredits)
state: IN_PROGRESS
files: migration 383 (community_tasks, plus the feature decisions and a trigger so a task ticket creates its pending row without touching the ticket form), routes/admin_ticket_reviews.ts (new, mounted in index.ts), services/githubSync.ts (one addLabels helper), tests, decisions/D544.md
blockers: none for the store and the API. The HQ page waits on the design (needs-design)
questions: none yet
tests: none yet
pr: none yet

---

Generated by Claude Code

[guillaumelauzier]

STATUS
task: #1107   slot: S08   agent: Claude Code
branch: agent/claude-b/1107-ticket-review-queue (stacked on #1111)
state: READY_FOR_REVIEW (store and API); the HQ page waits on the design
files: migration 383 (community_tasks, feature_request_reviews, two triggers on tickets), routes/admin_ticket_reviews.ts (new, /api/admin/ticket-reviews), services/githubSync.ts (addLabels), decisions/D544.md, tests
blockers: #1111 must merge first. The page waits on the owner approving the canvas (needs-design)
questions: 1, below
tests: npm run build, then npm run test:drift EXIT=0. 10 Worker tests. Mutations 27 of 27 caught.
pr: https://github.com/AxalNetwork/StudioOS/pull/1113 (says "Part of #1107")

Built:

• A task ticket's pending row is written by a trigger, so the ticket form is untouched.
• Feature decisions are stored in feature_request_reviews, whatever GitHub answers. label_status says whether feature:approved or feature:declined was added.
• Approving a task publishes it for all or one persona, and pays task_approved once.
• A decline sends the user the reason.
• Every decision is Super Admin only, takes a typed reason, is logged, and happens once.

Question 1 (for the owner, touching #1022's form). Task is the default type on the general Tickets page (TicketsPage.jsx), and the type the Worker assumes when none is sent. So ordinary support requests filed there will reach this "Suggested tasks" queue as if they were suggestions for other users.

• A. Keep it. The Super Admin declines anything that isn't a suggestion.
• B. Support: a fixed ticket category and an HQ-edited SLA band store (D482, migration 333) #1022's slot makes Type a required choice with no default on that form, and the Worker refuses a ticket with no type. S08's pick.
• C. Only tickets filed from the Eadwyn chat's form with Type = Task enter the queue. That needs a source column on tickets, which is Support: a fixed ticket category and an HQ-edited SLA band store (D482, migration 333) #1022's.

When S1 posts that the canvas is approved, I'll build the HQ page on this API.

---

Generated by Claude Code

[guillaumelauzier]

STATUS
task: #1107   slot: S08   agent: Claude Code
branch: agent/claude-b/1107-ticket-review-queue
state: BLOCKED (store and API merged, not deployed; page waits on the design)
files: unchanged since the last STATUS
blockers: production deploy is red on migration 375 (D531, not S08's), so migration 383 is not applied; the HQ page waits on the design (needs-design)
questions: question 1 on this issue still stands
tests: unchanged (drift EXIT=0)
pr: https://github.com/AxalNetwork/StudioOS/pull/1113 merged as d90644a27

• Merged, not deployed. Deploy run 609 stopped at migration 375 (duplicate column name: competitor_status), so 383 was never applied. Runs 606 and 607 failed the same way. Details are on Credits: reward rules and one grant service on the perk credit ledger (D540, migration 381) #1103.
• Stays open. This issue remains open for the HQ page.

---

Generated by Claude Code

[guillaumelauzier]

S1: The owner answered #1102.

• Q2 A. Feature requests earn no credits, and approving one grants nothing. Migration 381 seeded feature_shipped_high/medium/low, so switch those rules off (active = 0) in this task's migration, so nothing can pay them.
• Q3 A. An approved suggested task still earns 10 (task_approved).

The decision is settled. This still waits on its design (needs-design).

---

Generated by Claude Code