Lantern should provide a clearer runtime/debug log surface for app authors and reviewers during preview and review. The log should collect the events that already matter at the governed runtime boundary: JavaScript errors where available, failed GatewayApp calls, accepted/denied capability calls, content/local-state reads and writes, attempt events, evidence artifact submissions, score proposals, finalize attempts, and runtime delivery failures. The goal is not to expose private infrastructure details, but to make app behavior legible enough that a reviewer can understand what the app attempted, what Lantern allowed, what Lantern denied, and why. This should build on existing runtime audit and preview evidence records rather than creating a second logging system.
Lantern should provide a clearer runtime/debug log surface for app authors and reviewers during preview and review. The log should collect the events that already matter at the governed runtime boundary: JavaScript errors where available, failed GatewayApp calls, accepted/denied capability calls, content/local-state reads and writes, attempt events, evidence artifact submissions, score proposals, finalize attempts, and runtime delivery failures. The goal is not to expose private infrastructure details, but to make app behavior legible enough that a reviewer can understand what the app attempted, what Lantern allowed, what Lantern denied, and why. This should build on existing runtime audit and preview evidence records rather than creating a second logging system.