flyquery 26.10.2

flyquery 26.10.2 combines bounded query grounding, privacy fixes and adoption of fireflyframework-agentic 26.10.1. The qualified pyfly 26.06.113 runtime is retained.

• Query grounding uses bounded column-value catalogs and relation candidates; conversation turns preserve their snapshot selections. Candidate probes pass the registered-table fence before execution.
• Missing or unauthorized dataset scope is rejected before retrieval or model calls, with a caller-scoped audit record.
• PII scanning checks original samples before filtering and retained profile values before embedding. Redact/reject stores an explicit empty-list denial, preventing profiles from reintroducing protected values into schema knowledge. Original source files remain unchanged.
• FLYQUERY_PROMPT_CACHE now affects actual agent construction. Enabled mode adds Anthropic instruction-cache hints; user messages, tool results and answers are not memoized. Agentic supplies the default logging/observability middleware once.
• Seven agent SDK list operations now deserialize their existing table, search, snapshot, object, change, dataset and conversation envelopes. Python and Java examples and response types match the API.
• The server dependency graph is tracked in uv.lock, checked before frozen installation, with public first-party sources. Nineteen historical shared-source baselines and two reviewed service variants retain source-drift checks.

Local qualification: 451 unit tests; 109 native integration tests using PostgreSQL/pgvector, Redis and pinned-source MinIO; Python SDK 25 tests and type checks; Java 25 Maven verification. Both generated SDKs read all seven typed pages against the installed service. All fourteen changed Python and Java documentation examples compile and run against that API. Native token checks, foreign-tenant visibility, SUM60, SSE event ordering, persisted history and result Parquet contents were also checked.

Fifteen optional GCS/Azure storage scenarios remain unqualified, and paid-model tests were deliberately excluded. A nonempty executed candidate is a heuristic, not proof that its entities or filters match the question. The engine does not enforce its statement-timeout setting or provide an operating system sandbox. Remote object-store DuckDB reads are not accepted by these local registered-file tests. PII detection is limited to sampled or retained profile values and the configured scanner.

User-route authentication belongs to the deployment gateway; tenant/workspace headers select scope and are not credentials. Agent routes verify issued agent tokens and scopes.