Expose IBM i source-member edit interfaces for VS Code and IBM BOB ecosystem

VSCODE (code for IBM i)  need safe and fast source-member editing, but today we do not have a way to open, lock, save/update source member via these editors. In essence we need to:

1. Issue an OVRDBF to the source file and member
2. Issue a remote SQL SELECT to read the member
3. Generate a huge SQL INSERT statement to copy the entire dataset back into the member, replacing its content.

IBM RDi has stronger internal workflows for member edit/lock/update behavior, but there is no clearly documented, supported, public interface that VS Code and the CODE for IBM i team can leverage. 

Request:
Please expose a supported public interfaces for source member editing that can be used by:

1. IBM BOB ecosystem
2. VS Code extensions
3. Other IBM i remote IDE clients

Likely existing building blocks IBM can surface:

1. Member-targeted database access for source members.
2. Existing object/member lock primitives and host server lock handling.
3. Existing save/rewrite flows used by IBM RDi tooling for source members.

What should be exposed as public, documented APIs

1. LOCKSRC
   Acquire lock lease for one member and return lock token plus lease expiry.
2. HEARTBEATSRC
   Renew lock lease while editor session is alive.
3. READSRC
   Return ordered source rows plus version token/checksum.
4. SAVESRC
   Accept either full replace or delta operations and apply atomically.
5. UNLOCKSRC
   Explicit lock release.

Critical behavior requirements

1. Lease-based locking with automatic expiry to prevent orphaned locks after client crash/power loss or unexpected disconnect.
2. Optimistic concurrency guard using version token from READSRC.
3. Support for large source members and delta-friendly saves.
4. Clear machine-readable error model for things like lock expired, lock conflict, authority, and data conversion failures.

Why this matters

1. Better parity between IBM tools and open ecosystem tooling.
2. Lower host/network load for large members.
3. Fewer stale-lock incidents and support tickets.
4. Faster and safer editing experience for IBM i customers.

I would prefer an SQL-first approach if possible, but I am fully capable of creating SQL UDTF/Procs from hardened IBM i APIs, including:

1. Procedures for lock lifecycle and save operations.
2. UDTF for row-ordered member reads.
3. Optional version token and lease token included for locking protocols.