Expose all functions by default in decision service

[mengwong]

Summary

Changes the decision service to expose all functions from L4 files, not just those with explicit @export markers. This aligns the decision service behavior with the core library.

Motivation

Previously, the decision service required explicit @export annotations to expose functions via the REST API. This was inconsistent with the core library (L4.Export), which exposes the topmost function as default when no @export markers are present.

This created a barrier for users getting started with L4 - they had to learn about @export annotations before their functions would be accessible through the API.

Changes

• Removed explicitExportsOnly filter in jl4-decision-service/src/Examples.hs
• Now uses getExportedFunctions directly from L4.Export
• Inherits core library behavior:
  • When no @export markers exist: exposes topmost function as default
  • When @export markers exist but no default: marks topmost as default
  • When explicit default exists: uses as-is
• Cleaned up unused imports (L4.Annotation, DescFlags, ParsedDesc)

Behavior

Before:

GIVEN x IS A NUMBER
GIVETH A NUMBER
DECIDE square x IS x * x

Result: No functions exposed via API ❌

After:

GIVEN x IS A NUMBER
GIVETH A NUMBER
DECIDE square x IS x * x

Result: square exposed as default function ✅

Testing

• Builds successfully (cabal build jl4-decision-service)
• Verified via REPL that functions are recognized
• Tested with L4 file containing no @export markers

Impact

• Makes L4 programs more accessible for beginners
• Reduces boilerplate for simple programs
• Maintains backward compatibility (programs with @export work as before)

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.