Create doc Reference for declarative tools output filtering

[yada]

We need to document the reference specification for the Tools Output Filtering configuration schema (coming in 0.0.12). This issue tracks the creation of the reference syntax, grammar rules, and configuration boundaries required for precise token optimization and deterministic tool scoping.

This will live under our technical reference doc section (e.g., docs/reference/spec-outtools-filtering.md). TBD

Reference Content Requirements

The reference document must formally map out the configuration structure related to the Implementation -> reshaprio/reshapr#10

[Abdul-Moiz31]

Hey @yada I can take this up .

[yada]

Welcome, @Abdul-Moiz31. Please submit a PR for review and sign it to pass the DCO check (mandatory).

[Abdul-Moiz31]

Thankyou so much @yada !! Will Do .

[yada]

@Abdul-Moiz31: PR merged. Thank you very much for this contribution, which is greatly appreciated.

I just reopened the issue so that you can update the doc with the latest comment from @lbroudoux :

[docs/references/spec-outtools-filtering.md](https://github.com/reshaprio/reshapr.io/pull/17/files/234d208889d66bdddfa213257676ce22f8eaf1a4#diff-665f4f1dac50eebd1e8f6aa49d42dac7d1fb40efc56e4d164cafa00843470615)

- The value of `convertToToon` **must** be `true`,
- It is applied **last**, after `jsonRetain` and `jsonPatches` have run,
- It can be used alone, or combined with `jsonRetain` and/or `jsonPatches`.
Member
@[lbroudoux](https://github.com/lbroudoux)
lbroudoux
[yesterday](https://github.com/reshaprio/reshapr.io/pull/17#discussion_r3317746335)
It could be nice to put more emphasis on the fact that it can be used without json operations and whatever the kind of backend.

Happy to have an update from you on this point, ask questions in the issue if you need further details before doing your PR ;)

[Abdul-Moiz31]

Hi @yada and @lbroudoux ! Thank you for the feedback on PR #17.
and apologies for delya we have our Eid holidays

I'll be opening a follow-up PR to add more emphasis on the fact that convertToToon can be used standalone — without any jsonRetain or jsonPatches — and that it applies uniformly across REST, GraphQL, and gRPC backends regardless of backend protocol.

Will include a dedicated standalone example to make this clearer for end users.

is there anything else or its fine ?