Added basic import structure for library usage

[CodyCBakerPhD]

fix #389

@asmacdo Here you go

[CodyCBakerPhD]

Well, one second - it's behaving a bit oddly in kernel ATM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.83%. Comparing base (3756590) to head (4ca4b23).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #390      +/-   ##
==========================================
+ Coverage   91.81%   91.83%   +0.01%     
==========================================
  Files          15       15              
  Lines        1112     1114       +2     
  Branches      138      138              
==========================================
+ Hits         1021     1023       +2     
  Misses         69       69              
  Partials       22       22              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

Exposes a minimal public API surface for the con_duct package by re-exporting the main execution entrypoint and explicitly defining module exports.

Changes:

• Re-export execute from duct_main at the package root (con_duct.execute).
• Add __all__ to explicitly define the intended public exports (execute, __version__).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[CodyCBakerPhD]

@asmacdo OK good to go - just note that duct_main does need to be relabeled as private (this one out of necessity for completerlib, not just convention) since it is the source of the execute function and must be imported into the namespace for that

[asmacdo]

@CodyCBakerPhD IMO this looks good, but I'm wondering if we've restricted it enough. Should the other files (ie cli ls json_utils, plot, pprint_json) also be made private for now? I'll go ahead and merge, but I suspect we should do a followup and perhaps reopen #389

[CodyCBakerPhD]

@asmacdo So, this back to how strictly you want to follow convention

Technically, anything not included in the scoped init of this PR should be marked private (both modules and internal methods / classes / globals)

But as it is, the scope hides them well enough since they are not directly imported by the execute method of _duct_main.py, so they are 'private' simply because they are 'not found' by common searchers

I think the VSCode completion is more sensitive to folder existence than PyCharm or ipython are so that would be the exception I think