ai-engineering-from-scratch/phases/19-capstone-projects/09-code-migration-agent/quiz.json at main · rohitg00/ai-engineering-from-scratch · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
{
  "lesson": "09-code-migration-agent",
  "title": "Capstone 09 — Code Migration Agent (Repo-Level Language / Runtime Upgrade)",
  "questions": [
    {
      "stage": "pre",
      "question": "Why does the pipeline combine a deterministic substrate with an agent layer rather than using just one?",
      "options": [
        "Agents alone are faster than recipes",
        "OpenRewrite or libcst handles 70-80% of mechanical rewrites safely and cheaply, leaving the agent for the ambiguous long tail",
        "Determinism is needed only for the build system",
        "Deterministic recipes are slower than LLMs"
      ],
      "correct": 1,
      "explanation": ""
    },
    {
      "stage": "pre",
      "question": "What signal does the pipeline use as ground truth for a successful migration?",
      "options": [
        "Agent self-grading on a rubric",
        "Reviewer approval on the PR",
        "Diff size below a hard limit",
        "Green CI in the sandbox without a coverage regression beyond a small threshold"
      ],
      "correct": 3,
      "explanation": ""
    },
    {
      "stage": "check",
      "question": "Which budget caps does the agent loop enforce per repo?",
      "options": [
        "30 minutes wall-clock, $8 cost, and 20 agent turns",
        "1 hour wall-clock and 100 turns",
        "Unlimited time and cost; abort only on errors",
        "No turn limit, $100 ceiling"
      ],
      "correct": 0,
      "explanation": ""
    },
    {
      "stage": "check",
      "question": "What gate fires when coverage drops more than about 2% after migration?",
      "options": [
        "The deterministic substrate replays its recipes",
        "The repo gets filed under a coverage_regression failure class instead of opening a clean PR",
        "The agent automatically force-pushes a fix",
        "The reviewer is bypassed"
      ],
      "correct": 1,
      "explanation": ""
    },
    {
      "stage": "check",
      "question": "Why is the failure taxonomy treated as a deliverable rather than a side artifact?",
      "options": [
        "It replaces the test suite",
        "It is required by GitHub branch protection",
        "It satisfies a compliance checklist",
        "It groups failed repos by class so future recipe authors can target the top failure modes"
      ],
      "correct": 3,
      "explanation": ""
    },
    {
      "stage": "post",
      "question": "Which public benchmark does the capstone target for Java 8 to 17 migration?",
      "options": [
        "MMLU-Pro",
        "MigrationBench from Amazon",
        "ViDoRe v3",
        "SWE-bench Pro"
      ],
      "correct": 1,
      "explanation": ""
    },
    {
      "stage": "post",
      "question": "What does the agent integration rubric measure about the fix distribution?",
      "options": [
        "Number of dependencies pinned",
        "The number of force-pushes per repo",
        "The fraction of fixes handled by OpenRewrite versus authored by the agent layer",
        "Tokenization speed of the source file"
      ],
      "correct": 2,
      "explanation": ""
    }
  ]
}