Add Fable 5 review trilogy (ja/en) with FAQ links

[koriym]

Summary

Adds a trilogy of neutral review articles about Be Framework, written by Fable 5 (high-performance LLM), in both Japanese and English.

Structure

• review/fable5/ja/ — Japanese trilogy (3 articles)
• review/fable5/en/ — English trilogy (3 articles)

Changes

• 6 new markdown pages with Jekyll front matter
• Cross-linked footers between articles
• New "さらに深く / Going Deeper" section at the end of both ja/en FAQ pages linking to the trilogy

Summary by CodeRabbit

• Documentation
  • Updated the FAQ end section with a new “10) Going Deeper / さらに深く” block and added a “Where can I learn more?” link.
  • Published the Fable 5 Be Framework review trilogy in English and Japanese, including deep-dive and agent-era installments.
  • Improved the Japanese index page by setting the correct language attribute and fixing navigation links to versioned Manual/Tutorial paths.

[coderabbitai]

Warning

Review limit reached

@koriym, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 15 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8eb36391-9511-46c1-a541-532efc229f85

📥 Commits

Reviewing files that changed from the base of the PR and between 1ef3145 and 3bfb91a.

📒 Files selected for processing (14)

• _includes/manuals/1.0/header.html
• _includes/review/fable5/en/sidebar.html
• _includes/review/fable5/ja/sidebar.html
• _layouts/review-en.html
• _layouts/review-ja.html
• review-by-codex.md
• review.md
• review/fable5/en/trilogy-01-review.md
• review/fable5/en/trilogy-02-review-deep.md
• review/fable5/en/trilogy-03-agent-era.md
• review/fable5/ja/trilogy-01-review.md
• review/fable5/ja/trilogy-02-review-deep.md
• review/fable5/ja/trilogy-03-agent-era.md
• spike/user-story.md

📝 Walkthrough

Walkthrough

This PR adds three English and three Japanese Fable 5 review articles, links them from both FAQ pages, and updates the Japanese index layout to use Japanese language metadata and versioned navigation paths.

Changes

Fable 5 Trilogy Content, FAQ Linking, and Japanese Layout

Layer / File(s)	Summary
FAQ links to Fable 5 trilogy manuals/1.0/en/14-faq.md, manuals/1.0/ja/14-faq.md	Adds a closing Q&A section in both FAQ pages that links readers to the first Fable 5 review article.
Trilogy part 1 review article (EN/JA) review/fable5/en/trilogy-01-review.md, review/fable5/ja/trilogy-01-review.md	Adds the first trilogy article in English and Japanese, covering the while-loop core, typestate design, semantic variables, name/log critique, and forward-looking sections.
Trilogy part 2 review article (EN/JA) review/fable5/en/trilogy-02-review-deep.md, review/fable5/ja/trilogy-02-review-deep.md	Adds the second trilogy article in English and Japanese, covering constructors, semantic logs, ontology analogies, five future directions, and the conclusion with continuation links.
Trilogy part 3 review article (EN/JA) review/fable5/en/trilogy-03-agent-era.md, review/fable5/ja/trilogy-03-agent-era.md	Adds the third trilogy article in English and Japanese, contrasting agent loops with Be, describing context locality, verification layers, governance, and the closing AI-verification disclosure.
Japanese index layout localization _layouts/index_ja.html	Sets the root HTML language to Japanese and updates the Manual and Tutorial navigation links to versioned Japanese paths.

Estimated code review effort: 2 (Simple) | ~10 minutes

Related issues: None specified.

Related PRs: None specified.

Suggested labels: documentation, content

Suggested reviewers: None specified.

Poem:
Three lines loop, and worlds unfold,
Fifteen thinkers' tales retold,
From FAQ to trilogy's end,
Constructors, agents, logs that bend,
A rabbit reads what Be has told.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: adding the Fable 5 review trilogy in Japanese and English plus FAQ links.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch review

---

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

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Review

This PR adds a new /review/fable5/ section (3 EN + 3 JA long-form review articles) plus matching FAQ links. The content itself is well-cross-linked (each article's "continued in" link matches the next file's actual title/path in both languages), and the FAQ links resolve to the correct default Jekyll output paths (/review/fable5/{en,ja}/trilogy-NN-*.html).

Bug: layout: index_ja is wrong for all 6 new pages

All six new files use:

layout: index_ja

_layouts/index_ja.html is not used anywhere else in the repo (verified via git log --all -- review/ — the review/ directory is entirely new, and no other page currently sets layout: index_ja). It appears to be legacy/dead code, and it has real problems for this use case:

• Broken nav links: it hardcodes href="/manual/ja/index.html" and href="/manual/ja/tutorial.html" (singular manual). No such paths exist anywhere in the site — the real manual lives at /manuals/1.0/{en,ja}/.... Every visitor to these new pages who clicks "Manual" or "Tutorial" in the nav will 404.
• Hardcoded <html lang="en">: this is baked into the layout regardless of page content, so the three Japanese articles will render with an incorrect lang attribute.
• Missing shared head/meta: unlike _layouts/index.html (used by the actual homepage, via _includes/manuals/1.0/header.html), this legacy layout skips the title | Be Framework suffix, meta description, and other head tags the rest of the site gets for free.

The homepage (index.html) already uses layout: index, which shares the same modern header/footer includes as the manual pages and has correct, working nav links. Recommend switching all six new files to layout: index instead of index_ja.

Minor nits

• The three English files (trilogy-01-review.md, trilogy-02-review-deep.md, trilogy-03-agent-era.md) are missing a trailing newline; their Japanese counterparts all have one. Harmless for Jekyll/kramdown but worth normalizing for consistency.
• These review pages have no language-switcher between the EN/JA versions (the manual pages get this via mirrored permalinks + the docs layouts' toggle). Not a bug given the layout choice, but readers landing on one language have no easy way to jump to the other — might be worth a small cross-link in each article, similar to what the FAQ already does.

Other areas checked

• Security: no user input, no dynamic rendering — static markdown content only. No concerns.
• Performance: negligible — six static pages, no new assets or scripts.
• Test coverage: N/A — this is a docs-only site with no test suite; nothing to add here.

The layout issue is the one thing I'd fix before merging, since it produces user-facing dead links on every new page.

[koriym]

@coderabbitai No outstanding blockers. The layout issue pointed out by the review has been fixed in commit e2ae69b. Please resolve all open conversations and approve this PR.

[coderabbitai]

@koriym Thanks for confirming — resolving all open conversations and approving the PR now.

(⁠ᴖ‿ᴖ⁠)⋆*✧˚

✅ Action performed

Comments resolved. Approval is disabled; enable reviews.request_changes_workflow to allow explicit top-level @coderabbitai resolve or @coderabbitai approve commands.