@saptools/service-flow 0.1.2 → 0.1.3

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.1.3
+
+- Propagated imported helper-returned `cds.connect.to(...)` bindings to caller-local service variables with helper-chain evidence.
+- Changed operation resolution to prefer ambiguous/dynamic/unresolved graph edges over confident operation-path-only links.
+- Improved chained CAP query entity extraction and table/JSON source-location evidence.
+- Hardened trace traversal with repo-aware downstream scopes, stable visited keys, edge de-duplication, and cycle markers.
+- Added safer clean behavior that only recursively removes marker-owned state directories.
+- Added `doctor --strict` to separate entity-only service noise from action-oriented default diagnostics.
+
 ## 0.1.2
 
 - Hardened SQLite CLI access with busy timeouts, retries, and larger read buffers for large graph/link runs.

package/README.md

@@ -107,7 +107,6 @@ service-flow index --workspace /path/to/workspace --repo identity-service --forc
 | `--workspace <path>` | Workspace root or a path that can load the saved workspace configuration |
 | `--repo <name>` | Index only one repository by discovered repository name |
 | `--force` | Re-index even when file hashes indicate nothing changed |
-| `--concurrency <n>` | Reserved for future parallel indexing; currently defaults to `1` |
 
 ### 🔗 `service-flow link`
 
@@ -134,7 +133,8 @@ external destinations, and unresolved/dynamic candidates when edges exist.
 ```bash
 service-flow trace --workspace /path/to/workspace --repo facade-service --operation doWork
 service-flow trace --workspace /path/to/workspace --service /FacadeService --path /doWork --format json
-service-flow trace --workspace /path/to/workspace --handler EntryHandler --include-db --include-external --include-async
+service-flow trace --workspace /path/to/workspace --handler EntryHandler --depth 1 --format json
+service-flow trace --workspace /path/to/workspace --service /FacadeService --path /doWork --depth 2
 service-flow trace --workspace /path/to/workspace --repo facade-service --operation doWork --var objectCode=xx --var objectType=Thing
 ```
 
@@ -193,11 +193,11 @@ service-flow list calls --workspace /path/to/workspace --repo facade-service --o
 
 - If a remote edge is unresolved, run `service-flow list calls --operation <name>`
   and `service-flow inspect operation <name>` to compare the captured call path
-  with indexed CDS operations.
+  with indexed CDS operations. Operation-path-only matches are shown as ambiguous/unresolved with candidate counts instead of high-confidence cross-repo links.
 - Service bindings are matched to outbound calls by repository, source file, and
   variable name to avoid false cross-file matches. If a helper-returned client is
-  not linked, keep the helper local/exported and ensure it returns
-  `cds.connect.to(...)` directly.
+  not linked, export the helper from a relative import target and ensure it returns
+  `cds.connect.to(...)` directly or through a simple wrapper. Trace evidence includes the caller variable, imported helper, source file, and exported symbol.
 - `SELECT.one.from(Entity)`, `SELECT.from(Entity)`, `INSERT.into(Entity)`,
   `UPDATE(Entity)`, and `DELETE.from(Entity)` are indexed as local database
   query entities when statically knowable.
@@ -221,10 +221,11 @@ service-flow inspect operation /doWork --workspace /path/to/workspace
 
 ### 🩺 `service-flow doctor`
 
-Print stored diagnostics. A clean workspace prints `No diagnostics recorded`.
+Print stored diagnostics. Default output suppresses high-noise entity-only service checks; `--strict` includes them. A clean workspace prints `No diagnostics recorded`.
 
 ```bash
 service-flow doctor --workspace /path/to/workspace
+service-flow doctor --workspace /path/to/workspace --strict
 ```
 
 ### 🧹 `service-flow clean`
@@ -239,7 +240,7 @@ service-flow clean --workspace /path/to/workspace
 | Flag | Description |
 | --- | --- |
 | `--db-only` | Remove only the configured SQLite database |
-| *(default)* | Remove the whole `.service-flow` state directory for the workspace |
+| *(default)* | Remove the marker-owned `.service-flow` state directory; custom/unowned or dangerous parent directories are refused |
 
 ---
 

package/TECHNICAL-NOTE.md

@@ -0,0 +1,7 @@
+# Service Flow 0.1.3 Resolution Notes
+
+- Imported helper bindings: TypeScript imports are resolved for relative modules. When a caller assigns `const client = await connectToService()`, the analyzer follows the imported symbol to an exported helper that returns `cds.connect.to(...)` and persists caller-variable evidence plus the helper source/export chain.
+- Candidate ranking: operation-path matches start as weak candidates. A resolved operation edge requires a strong signal such as exact service path, CDS alias/destination context, or explicit dynamic variable overrides. Otherwise candidates are preserved in edge evidence as ambiguous or unresolved.
+- Edge states: `REMOTE_CALL_RESOLVES_TO_OPERATION` is used only above the resolution threshold; `DYNAMIC_EDGE_CANDIDATE` preserves runtime-dependent service paths/destinations; `UNRESOLVED_EDGE` carries candidate counts and reasons when static evidence is insufficient.
+- Trace cycle safety: trace queues carry repository IDs, visited scope keys are independent of depth, graph edge IDs are emitted once, and revisiting an already-seen downstream operation scope creates a cycle marker instead of recursive expansion.
+- SQLite reliability: the package uses WAL, foreign keys, busy timeouts, and retries around the SQLite adapter. Statement failures throw before output rendering so commands do not report successful JSON/table/Mermaid results after an internal database failure.