[2026-03-15 11:53] - Updated by Junie
{
    "TYPE": "correction",
    "CATEGORY": "gRPC config",
    "EXPECTATION": "Use only the v2 gRPC server configuration and remove v1 config paths/fields.",
    "NEW INSTRUCTION": "WHEN editing gRPC server configuration THEN remove v1 config and use only v2 fields"
}

[2026-03-15 13:02] - Updated by Junie
{
    "TYPE": "correction",
    "CATEGORY": "gRPC config",
    "EXPECTATION": "Use only the v2 gRPC server configuration and remove v1 config paths/fields.",
    "NEW INSTRUCTION": "WHEN editing gRPC server configuration THEN remove v1 config and use only v2 fields"
}

[2026-03-15 13:34] - Updated by Junie
{
    "TYPE": "negative",
    "CATEGORY": "tarball download",
    "EXPECTATION": "The tarball download should succeed, or clearly show an error in the browser when it fails.",
    "NEW INSTRUCTION": "WHEN implementing download endpoints THEN return non-200 on failure with an explanatory message"
}

[2026-03-15 13:52] - Updated by Junie
{
    "TYPE": "negative",
    "CATEGORY": "tarball download",
    "EXPECTATION": "If the cert/key tgz cannot be generated correctly, the response should not be a 200 attachment; it should clearly show an error in the browser.",
    "NEW INSTRUCTION": "WHEN download content is invalid or generation fails THEN return non-200 with visible error page"
}

[2026-03-15 13:55] - Updated by Junie
{
    "TYPE": "correction",
    "CATEGORY": "root cause update",
    "EXPECTATION": "The tgz download failure was caused by the aria2 download manager, not the server.",
    "NEW INSTRUCTION": "WHEN user reports aria2 caused the issue THEN acknowledge client-side cause and reassess server changes"
}