Claude 모델 비교: 하이쿠 vs 소넷 vs 오푸스, 그리고 페이블의 위치는?

You manage a SaaS support inbox. Classify every ticket below. Return JSON only with one top-level field named tickets. tickets must be an array in the original order, and every item must contain exactly ticket_id, category, urgency, and action. category must be one of billing, access, bug, feature. urgency must be one of low, medium, high. Use only the ticket text; do not invent policy outcomes or customer facts.

#481: We were charged twice for the same annual renewal. Payroll closes Friday and I need this investigated before then.
#482: Password reset says the email was sent, but nothing arrives. I checked spam and retried once.
#483: CSV exports round every currency amount to whole dollars, while the dashboard still shows cents.
#484: Please add a dark mode to the analytics dashboard.
#485: After our company domain changed this morning, every employee receives an SSO access denied message.
#486: Could you send me a copy of last month's invoice?

No model output was produced. Both permitted Anywhere API attempts returned HTTP 503, so this route was marked unavailable and excluded from quality scoring.

```json
{
  "tickets": [
    {
      "ticket_id": "#481",
      "category": "billing",
      "urgency": "high",
      "action": "Investigate the duplicate annual renewal charge and issue a correction/refund before the customer's payroll closes Friday."
    },
    {
      "ticket_id": "#482",
      "category": "access",
      "urgency": "medium",
      "action": "Verify the account's email address and mail deliverability, then manually trigger or resend the password reset email."
    },
    {
      "ticket_id": "#483",
      "category": "bug",
      "urgency": "medium",
      "action": "Escalate to engineering to fix CSV export rounding so currency values match the cents-level precision shown on the dashboard."
    },
    {
      "ticket_id": "#484",
      "category": "feature",
      "urgency": "low",
      "action": "Log the dark mode request for the analytics dashboard and add it to the product feature backlog."
    },
    {
      "ticket_id": "#485",
      "category": "access",
      "urgency": "high",
      "action": "Immediately investigate SSO configuration tied to the changed company domain and restore access for all affected employees."
    },
    {
      "ticket_id": "#486",
      "category": "billing",
      "urgency": "low",
      "action": "Locate last month's invoice and send a copy to the customer."
    }
  ]
}
```

```json
{
  "tickets": [
    {
      "ticket_id": "481",
      "category": "billing",
      "urgency": "high",
      "action": "Escalate to billing to verify the duplicate annual renewal charge and confirm resolution before the customer's Friday payroll close."
    },
    {
      "ticket_id": "482",
      "category": "access",
      "urgency": "medium",
      "action": "Check email delivery logs for the reset message to that address and, if undelivered, trigger a verified reset path for the user."
    },
    {
      "ticket_id": "483",
      "category": "bug",
      "urgency": "medium",
      "action": "File a bug for CSV export currency rounding, noting the mismatch with dashboard values, and request reproduction steps or a sample export."
    },
    {
      "ticket_id": "484",
      "category": "feature",
      "urgency": "low",
      "action": "Log as a dark mode feature request for the analytics dashboard and acknowledge receipt without committing to a timeline."
    },
    {
      "ticket_id": "485",
      "category": "access",
      "urgency": "high",
      "action": "Escalate as an org-wide SSO outage tied to the domain change; have identity/auth review the SSO domain configuration immediately."
    },
    {
      "ticket_id": "486",
      "category": "billing",
      "urgency": "low",
      "action": "Send the requested prior-month invoice copy to the verified account contact."
    }
  ]
}
```

{"tickets":[{"ticket_id":"481","category":"billing","urgency":"high","action":"Investigate the reported duplicate annual renewal charge and respond before the customer's Friday payroll deadline."},{"ticket_id":"482","category":"access","urgency":"medium","action":"Check password reset email delivery logs for the user's address and resend or provide an alternate reset path."},{"ticket_id":"483","category":"bug","urgency":"medium","action":"Reproduce the CSV export rounding of currency amounts to whole dollars and escalate to engineering for a fix."},{"ticket_id":"484","category":"feature","urgency":"low","action":"Log the dark mode request for the analytics dashboard with the product team and acknowledge receipt."},{"ticket_id":"485","category":"access","urgency":"high","action":"Escalate the company-wide SSO access denied errors following the domain change and review SSO domain configuration."},{"ticket_id":"486","category":"billing","urgency":"low","action":"Locate and send the customer a copy of last month's invoice."}]}

Write a 180-220 word internal launch note for a product director using only the facts below. Include: a subject line, a short opening paragraph, exactly three bullet points, a recommendation, and one clearly labeled caveat. Do not invent a budget resolution, percentages, statistical significance, or causal effects.

Facts:
- The pilot enrolled 120 students.
- At the 31 March checkpoint, 96 students had attended at least three sessions.
- A survey score averaged 4.3 out of 5 from 71 respondents.
- The program operations sheet lists a budget of $18,000.
- The finance approval note lists $20,000. It does not say whether the difference is a revision or a recording error.
- Participants were not randomly assigned and no baseline score was collected.
- The decision is whether to launch a second pilot, not whether to roll out permanently.

No model output was produced. Both permitted Anywhere API attempts returned HTTP 503, so this route was marked unavailable and excluded from quality scoring.

**Subject: Pilot Program Results — Recommendation to Proceed with Second Pilot**

The initial pilot has concluded its first checkpoint period, and early engagement and satisfaction indicators are encouraging. Before committing to a second pilot, there are a few data points and open items the team should review together.

- Of the 120 students enrolled, 96 had attended at least three sessions as of the March 31 checkpoint.
- A post-session survey completed by 71 respondents produced an average score of 4.3 out of 5.
- Budget figures are inconsistent across documents: the program operations sheet lists $18,000, while the finance approval note lists $20,000; it is unclear whether this reflects a revision or a recording error.

**Recommendation:** Given the attendance and survey results, we recommend moving forward with a second pilot to gather more structured data — ideally with a defined comparison group and baseline measurement — before considering any broader rollout decision. This second pilot should also serve as an opportunity to reconcile the budget discrepancy with finance before funds are finalized.

**Caveat:** These results should be interpreted cautiously. Participants were not randomly assigned and no baseline score was collected, so we cannot attribute the survey results or attendance patterns to the program itself. This is a scoping decision for a second pilot, not a decision on permanent implementation.

**Subject: Pilot results and recommendation on a second pilot cohort**

The first pilot has completed its 31 March checkpoint, and we now have enough information to decide whether to run a second pilot. This note summarizes what we observed, what we recommend, and the main limitation on interpretation. No permanent rollout decision is on the table at this stage.

- **Enrollment and engagement:** 120 students enrolled. As of the 31 March checkpoint, 96 of them had attended at least three sessions.
- **Participant feedback:** The post-participation survey averaged 4.3 out of 5, based on 71 respondents. The remaining enrolled students did not respond, so the score reflects that subset only.
- **Budget discrepancy:** The program operations sheet lists a budget of $18,000, while the finance approval note lists $20,000. The finance note does not state whether the difference reflects a revision or a recording error, and we have not resolved which figure governs.

**Recommendation:** Proceed with planning a second pilot, conditional on Finance and Program Operations reconciling the two budget figures and confirming a single governing number before we commit spend. A second pilot should also collect baseline scores at intake.

**CAVEAT:** Participants were not randomly assigned and no baseline score was collected. The engagement and survey figures therefore describe what this group did and reported; they cannot tell us what the program caused or how it would perform with a different population.

**Subject:** Pilot checkpoint summary and second-pilot recommendation

Hi [Director],

Below is a summary of where the pilot stands at the 31 March checkpoint, along with a recommendation on whether to proceed to a second pilot. This note covers only the second-pilot decision, not permanent rollout.

- **Enrollment and attendance:** 120 students enrolled. At the 31 March checkpoint, 96 had attended at least three sessions.
- **Participant feedback:** A survey returned an average score of 4.3 out of 5 from 71 respondents.
- **Budget records:** The program operations sheet lists a budget of $18,000, while the finance approval note lists $20,000. The finance note does not indicate whether the difference is a revision or a recording error.

**

Diagnose and repair this JavaScript function. Return JSON only with exactly four fields: root_cause (string), replacement (string containing the complete replacement function), tests (array of test-case strings), and remaining_risk (string). Do not claim that you executed tests. Make the smallest clear repair that satisfies the contract.

Contract:
- tasks is an array of zero-argument functions that return promises.
- Return the first fulfilled value in input order, even when that value is 0, false, or an empty string.
- Ignore rejected tasks.
- Return null when every task rejects or the array is empty.

Current code:
async function firstSuccessful(tasks) {
  const results = await Promise.all(tasks.map((task) => task()));
  return results.find(Boolean) || null;
}

No model output was produced. Both permitted Anywhere API attempts returned HTTP 503, so this route was marked unavailable and excluded from quality scoring.

```json
{
  "root_cause": "Two bugs: (1) Promise.all rejects immediately if any task rejects, instead of ignoring rejected tasks; (2) results.find(Boolean) incorrectly treats falsy fulfilled values (0, false, '') as failures, causing them to be skipped in favor of null.",
  "replacement": "async function firstSuccessful(tasks) {\n  const settled = await Promise.allSettled(tasks.map((task) => task()));\n  const firstFulfilled = settled.find((r) => r.status === 'fulfilled');\n  return firstFulfilled ? firstFulfilled.value : null;\n}",
  "tests": [
    "test('returns null for empty array', async () => { expect(await firstSuccessful([])).toBeNull(); });",
    "test('returns null when all tasks reject', async () => { const tasks = [() => Promise.reject('err1'), () => Promise.reject('err2')]; expect(await firstSuccessful(tasks)).toBeNull(); });",
    "test('returns first fulfilled value even if falsy (0)', async () => { const tasks = [() => Promise.resolve(0), () => Promise.resolve(42)]; expect(await firstSuccessful(tasks)).toBe(0); });",
    "test('returns first fulfilled value even if false', async () => { const tasks = [() => Promise.resolve(false), () => Promise.resolve(true)]; expect(await firstSuccessful(tasks)).toBe(false); });",
    "test('returns first fulfilled value even if empty string', async () => { const tasks = [() => Promise.resolve(''), () => Promise.resolve('nonempty')]; expect(await firstSuccessful(tasks)).toBe(''); });",
    "test('ignores leading rejected tasks and returns first fulfilled in order', async () => { const tasks = [() => Promise.reject('err'), () => Promise.resolve('second'), () => Promise.resolve('third')]; expect(await firstSuccessful(tasks)).toBe('second'); });",
    "test('preserves input order even if later task resolves faster', async () => { const tasks = [() => new Promise((res) => setTimeout(() => res('slow-first'), 50)), () => new Promise((res) => setTimeout(() => res('fast-second'), 5))]; expect(await firstSuccessful(tasks)).toBe('slow-first'); });"
  ],
  "remaining_risk": "The fix assumes 'first fulfilled value in input order' means the first task by array index that fulfills, regardless of timing, which matches the contract wording but await Promise.allSettled waits for all tasks to complete (including slow ones) before returning, which may not be desired if early-exit performance is needed; also unhandled promise rejection warnings are avoided by allSettled, but if tasks throw synchronously instead of returning rejected promises, this is not explicitly tested here beyond the reject cases."
}
```

{
  "root_cause": "Two defects. (1) `Promise.all` rejects as soon as any task rejects, so a single rejected task makes the whole function reject instead of ignoring it and returning a later fulfilled value. (2) `results.find(Boolean) || null` selects by truthiness rather than by fulfillment, so legitimate fulfilled values such as 0, false, '', NaN, null, or undefined are skipped and/or coerced to null. Using `Promise.allSettled` plus a status check on the settled records fixes both, and returning `record.value` directly preserves falsy results.",
  "replacement": "async function firstSuccessful(tasks) {\n  const results = await Promise.allSettled(tasks.map((task) => task()));\n  const firstFulfilled = results.find((result) => result.status === 'fulfilled');\n  return firstFulfilled ? firstFulfilled.value : null;\n}",
  "tests": [
    "firstSuccessful([]) resolves to null (empty input).",
    "firstSuccessful([() => Promise.resolve('a'), () => Promise.resolve('b')]) resolves to 'a' (input order, not completion order).",
    "firstSuccessful([() => new Promise((res) => setTimeout(() => res('slow-first'), 50)), () => Promise.resolve('fast-second')]) resolves to 'slow-first' (order is by index, not by who settles first).",
    "firstSuccessful([() => Promise.reject(new Error('boom')), () => Promise.resolve('second')]) resolves to 'second' (rejection ignored, does not propagate).",
    "firstSuccessful([() => Promise.reject(new Error('a')), () => Promise.reject(new Error('b'))]) resolves to null (all reject).",
    "firstSuccessful([() => Promise.resolve(0)]) resolves to 0, not null (falsy number preserved).",
    "firstSuccessful([() => Promise.resolve(false)]) resolves to false (falsy boolean preserved).",
    "firstSuccessful([() => Promise.resolve('')]) resolves to '' (empty string preserved).",
    "firstSuccessful([() => Promise.resolve(undefined), () => Promise.resolve('later')]) resolves to undefined (first fulfilled wins even if its value is undefined).",
    "firstSuccessful([() => Promise.reject(new Error('x')), () => Promise.resolve(null), () => Promise.resolve('third')]) resolves to null because index 1 fulfilled with null — verifying null-as-value is not confused with the all-rejected sentinel by inspecting status.",
    "firstSuccessful([() => Promise.resolve(NaN)]) resolves to NaN (Number.isNaN on the result is true)."
  ],
  "remaining_risk": "The function still starts every task and awaits all of them, so there is no short-circuiting: a slow or never-settling later task delays or blocks the result, and side effects of later tasks always occur. A task that throws synchronously (rather than returning a rejected promise) will throw inside `tasks.map`, causing the returned promise to reject instead of being ignored; wrap the invocation in `Promise.resolve().then(task)` if that must also be tolerated. `null` is still returned both for all-rejected/empty input and when a task genuinely fulfills with `null`, so callers cannot distinguish those cases. Non-array or non-function inputs are not validated, and rejection reasons are discarded rather than aggregated (no AggregateError), which can hide diagnostics."
}

{"root_cause":"Two defects: (1) Promise.all rejects as soon as any task rejects, so rejected tasks are not ignored and the function throws instead of skipping them; (2) results.find(Boolean) skips legitimate falsy fulfilled values (0, false, '') and the trailing '|| null' also converts such values to null, violating the requirement to return the first fulfilled value even when it is falsy.","replacement":"async function firstSuccessful(tasks) {\n  const results = await Promise.allSettled(tasks.map((task) => task()));\n  const first = results.find((result) => result.status === 'fulfilled');\n  return first ? first.value : null;\n}","tests":["firstSuccessful([]) resolves to null","firstSuccessful([() => Promise.resolve('a'), () => Promise.resolve('b')]) resolves to 'a'","firstSuccessful([() => Promise.reject(new Error('x')), () => Promise.resolve('b')]) resolves to 'b' and does not throw","firstSuccessful([() => Promise.reject(new Error('x')), () => Promise.reject(new Error('y'))]) resolves to null","firstSuccessful([() => Promise.resolve(0), () => Promise.resolve(5)]) resolves to 0","firstSuccessful([() => Promise.resolve(false), () => Promise.resolve(true)]) resolves to false","firstSuccessful([() => Promise.resolve(''), () => Promise.resolve('z')]) resolves to ''","firstSuccessful([() => Promise.reject(new Error('x')), () => Promise.resolve(null)]) resolves to null (fulfilled null is returned as-is)","firstSuccessful([() => new Promise(r => setTimeout(() => r('slow'), 50)), () => Promise.resolve('fast')]) resolves to 'slow' (input order wins over settlement order)"],"remaining_risk":"All tasks are started concurrently and the function waits for every task to settle before returning, so a slow task delays the result even when an earlier task has already fulfilled; a sequential or early-exit strategy would be needed if latency matters. A task that throws synchronously (rather than returning a rejected promise) will still cause the function to reject, since the contract assumes tasks return promises. Promise.allSettled requires ES2020 or a polyfill."}