paput-mcp 3.3.0 → 3.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -33,6 +33,7 @@ Extract reusable knowledge candidates from the current conversation or a user-sp
|
|
|
33
33
|
- Make titles concise and searchable.
|
|
34
34
|
- Write the body in Markdown.
|
|
35
35
|
- Do not use top-level Markdown headings (`# ...`) in the body. If headings help readability, start at `##`.
|
|
36
|
+
- The save API sits behind a WAF that inspects the request body, so write command, SQL, and markup examples as prose or pseudo-notation, not raw executable strings (an HTTP-fetch command with a URL, a union-style select, a leading script tag). Code fences do not help; raw strings get the request rejected with a 403.
|
|
36
37
|
- Include concrete procedures, causes, reasons, and decision criteria in the body.
|
|
37
38
|
- To make candidates reusable, naturally include decision criteria, applicability conditions, reasons, pitfalls, and verification methods where possible.
|
|
38
39
|
- Do not include project-specific specifications, implementation details, operational rules, code, secrets, or customer data.
|