///|
pub fn longform_handbook() -> String {
  (
    #|# MoonJSONPath Longform Handbook
    #|
    #|## 1. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 2. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 3. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 4. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 5. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 6. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 7. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 8. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 9. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 10. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 11. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 12. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 13. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 14. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 15. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 16. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 17. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 18. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 19. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 20. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 21. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 22. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 23. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 24. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 25. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 26. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 27. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 28. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 29. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 30. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 31. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 32. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 33. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 34. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 35. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 36. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 37. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 38. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 39. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 40. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 41. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 42. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 43. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 44. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 45. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 46. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 47. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 48. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 49. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 50. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 51. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 52. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 53. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 54. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 55. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 56. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 57. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 58. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 59. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 60. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 61. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 62. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 63. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 64. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 65. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 66. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 67. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 68. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 69. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 70. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 71. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 72. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 73. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 74. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 75. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 76. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 77. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 78. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 79. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 80. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 81. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 82. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 83. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 84. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 85. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 86. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 87. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 88. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 89. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 90. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 91. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 92. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 93. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 94. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 95. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 96. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 97. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 98. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 99. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 100. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 101. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 102. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 103. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 104. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 105. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 106. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 107. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 108. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 109. Project positioning
    #|
    #|- Topic: Project positioning for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 110. JSONPath basics
    #|
    #|- Topic: JSONPath basics for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 111. JSONPath filters
    #|
    #|- Topic: JSONPath filters for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 112. JSON Pointer usage
    #|
    #|- Topic: JSON Pointer usage for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 113. Patch workflows
    #|
    #|- Topic: Patch workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 114. CLI workflows
    #|
    #|- Topic: CLI workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 115. AI tooling workflows
    #|
    #|- Topic: AI tooling workflows for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 116. Configuration validation
    #|
    #|- Topic: Configuration validation for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 117. Documentation processing
    #|
    #|- Topic: Documentation processing for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 118. Contest submission
    #|
    #|- Topic: Contest submission for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 119. Testing strategy
    #|
    #|- Topic: Testing strategy for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
    #|## 120. Known limitations
    #|
    #|- Topic: Known limitations for reusable MoonBit JSON tooling.
    #|- Library angle: expose a typed API instead of forcing callers through shell commands.
    #|- CLI angle: keep file-based commands deterministic and easy to verify in CI.
    #|- Testing angle: add executable cases for values, pointers, and error behavior.
    #|- Submission angle: connect the feature to ecosystem value and Mooncakes readiness.
    #|- Limitation note: avoid claiming full jq compatibility or streaming stdin support.
    #|
  )
}