import-jsonl in server-hosted mode is fundamentally confusing

[zzmark]

I’m extremely frustrated with this behavior and the lack of clear documentation.

What is confusing

In a server-hosted setup, the CLI command import-jsonl appears to accept a local file path, but in practice it seems to send that path to the server, and then the server tries to read that “local” file.

This raises fundamental questions:

1. Is the path supposed to be interpreted on the client machine or on the server machine?
2. If the server is the one reading files, what exactly am I importing when I run this command locally?
3. If this is intentional, what is the actual value proposition of the hosted-server model for this workflow?
4. Why is there no explicit, unambiguous contract in docs/CLI help about:
   • where the path is resolved,
   • where the import is executed,
   • what users should do in remote-hosted deployments?

Why this is a problem

• The command name and argument shape strongly imply client-side file import semantics.
• Actual behavior appears to be server-side path resolution.
• This mismatch is a serious UX/design issue and leads to wasted user time and incorrect assumptions.
• This is not a minor papercut; it is a fundamental interface contract problem.

Request

Please either:

1. Clarify and document the current behavior clearly (client-path vs server-path, per deployment mode), with explicit examples,
   or
2. Fix the design so behavior matches user expectations (e.g., upload file content from CLI),
   or
3. Provide separate explicit commands/modes for:
   • importing a client-local file,
   • importing a server-local file.

Right now this is unclear enough to be actively misleading.