fix(docs): tn_cache configuration files to string

[outerlook]

Description

• Changed the enabled field in the tn_cache extension configuration from a boolean to a string in both the node operator guide and the README documentation, ensuring correctness.

Related Problem

• fix https://github.com/trufnetwork/truf-network/issues/1066

How Has This Been Tested?

Summary by CodeRabbit

• Documentation
  • Updated configuration examples in the documentation to represent the tn_cache extension's enabled option as a string ("true"/"false") instead of a boolean (true/false). This change is reflected consistently across all relevant documentation sections.

[coderabbitai]

Walkthrough

The documentation for the tn_cache extension was updated to change the representation of the enabled configuration value from a boolean (true) to a string ("true"). This update was applied to both the main node operator guide and the extension's README, with no changes to code or functional behavior.

Changes

Cohort / File(s)	Change Summary
Node Operator Guide Documentation docs/node-operator-guide.md	Updated configuration snippet to use "true" (string) instead of true (boolean) for enabled.
tn_cache Extension Documentation extensions/tn_cache/README.md	Changed all references of the enabled field in config examples and descriptions from boolean to string.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective	Addressed	Explanation
Update documentation to show enabled = "true" (string) for tn_cache extension (#1066)	✅

Poem

The cache was once enabled, just plain and true,
But now it wears quotes, as all strings must do!
Docs updated, guides aligned,
Configuration’s redefined.
A rabbit hops by, with a wink and a cheer—
“Your cache is now stringy, the docs are clear!” 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 545db39 and 58ff3d2.

📒 Files selected for processing (2)

• docs/node-operator-guide.md (1 hunks)
• extensions/tn_cache/README.md (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: acceptance-test
• GitHub Check: lint

🔇 Additional comments (5)

extensions/tn_cache/README.md (4)

12-12: Change to string literal is correct
TOML snippet now aligns with the string-only config requirement.

---

242-243: Good catch converting the disable example to a string
The shutdown instructions are now consistent with the new convention.

---

248-248: Config recap snippet updated correctly
String literal matches the new requirement.

---

289-289: Edge-case table updated correctly
The bypass condition now references "false" as a string, matching the rest of the doc.

docs/node-operator-guide.md (1)

473-473: Snippet now reflects string-only config – looks good
This keeps the operator guide in sync with the README change.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/cache-enable

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[holdex]

Time Submission Status

Member	Status	Time	Action	Last Update
@outerlook	❌ Missing	-	⚠️ Submit time	-
MicBun	✅ Submitted	15min	Update time	Jul 31, 2025, 6:45 AM

[holdex]

Bug Report Checklist

Status	Commit Link	Bug Author
❌ Not Submitted	–	–

@outerlook, please use git blame and specify the link to the commit link that has introduced this bug.

Send the following message in this PR: `@pr-time-tracker bug commit [link](url) && bug author @name`