🧪 Add missing tests for parse_in_surface_info

[undivisible]

🎯 What: Added tests for the parse_in_surface_info function in in_lang_parse/surface.rs to verify correct parsing of surface-level structure like packages, modules, imports, and orchestrations.
📊 Coverage: Tests now cover happy paths (parsing various top-level declarations like package, module, import, use, bind, capability, and parallel tasks) as well as error conditions (duplicate package/module, unknown syntax).
✨ Result: Improved reliability and test coverage for the initial parsing step of .in language files.

---

PR created automatically by Jules for task 9367590063555947948 started by @undivisible

---

Note

Low Risk
Test-only change with no runtime or parser behavior modifications.

Overview
Adds four unit tests in tests.rs that call parse_in_surface_info directly (not full parse_in_source), tightening coverage of the surface-only parse step.

One test asserts a happy path that bundles package, module, import, use, bind, capability, and a parallel block into the expected InSurfaceInfo fields (including orchestration task facts). Three tests lock in error paths: duplicate package, duplicate module, and unknown top-level syntax, each checking the corresponding error substring.

No production/parser code changes—tests only.

^{Reviewed by Cursor Bugbot for commit 981f7bd. Configure here.}

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_834ce521-d09d-4bb3-8332-0dd89e603efa)

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request