020 label jump obligation

// TEST: Phantom obligation tracking across label jumps
// STATUS: MUST_FAIL (fixed)
//
// BUG: When a label jump (@loop) occurs, phantom obligations from the
// current scope are not being checked. This allows resource leaks.
//
// EXPECTED: Compiler error - obligation not satisfied before @loop
// ACTUAL: Compiler error (KORU030) once obligations are enforced
//
// This test documents the gap discovered while building Orisha HTTP server.
// The `| failed |> @accept_loop(server: s)` branch leaks the connection.

const std = @import("std");

const Resource = struct { id: i32 };

~event create {}
| created *Resource<open!>

~proc create|zig {
    const r = std.heap.page_allocator.create(Resource) catch unreachable;
    r.* = .{ .id = 42 };
    return .{ .created = r };
}

~event use { res: *Resource<open> }
| ok *Resource<open>
| failed *Resource<open>

~proc use|zig {
    // Simulate sometimes failing
    if (res.id == 42) {
        return .{ .ok = res };
    }
    return .{ .failed = res };
}

~event close { res: *Resource<!open> }

~proc close|zig {
    std.heap.page_allocator.destroy(res);
}

// THE BUG: This flow should NOT compile!
// The `| failed |> @loop` branch has an open obligation that is never discharged.
~#loop create()
| created c |> use(c.res)
    | ok o |> close(o.res)
    | failed _f |> @loop()  // BUG! c.res has [open!] obligation, not discharged!

pub fn main() void {
    std.debug.print("Test compiled - BUG: should have been rejected!\n", .{});
}