* fix(notebooks): correct SUMMARIZE response parsing for get_description/get_summary The VfAZjd (SUMMARIZE) RPC returns a triple-nested structure: result = [[[summary_string], [[topics]], ...]] The previous parsing assumed: - Summary at result[0][0] (a string) — actually a list - Topics at result[1][0] — actually at result[0][1][0] This caused get_description() to always return an empty summary and no suggested topics, showing "No summary available" in the CLI. Fixed parsing to use: - Summary: result[0][0][0] - Topics: result[0][1][0] Updated all affected unit/integration tests to use the correct response structure (confirmed against the real API cassette in notebooks_get_summary.yaml). Fixes #147 * test(e2e): strengthen summary assertions to catch empty results * refactor(notebooks): simplify SUMMARIZE response parsing per review feedback * docs(rpc-reference): fix SUMMARIZE response structure (triple-nested) |
||
|---|---|---|
| .. | ||
| examples | ||
| cli-reference.md | ||
| configuration.md | ||
| development.md | ||
| python-api.md | ||
| releasing.md | ||
| rpc-development.md | ||
| rpc-reference.md | ||
| stability.md | ||
| troubleshooting.md | ||