Fall back to the description when the Hub's title is a fragment

[forrestlinfeng]

The bug

#24 put short_title in the header. A live session showed what that costs when the Hub's title is truncated:

[Evolution Memory] Object (EvoMap network):
1. Initialize pool with configurable minimum and maximum object capacity limits
2. Provide acquire method that returns available object or creates new if under maximum
…

Object is what got cut off, not what the gene is.

Why a length floor does not work

Forty titles across eight queries. Two are fragments — and a character count cannot tell them from a good title:

title	chars	verdict
自动化小	4	truncation
智能缓存优化	6	a complete title
Object	6	truncation
Generic Object Pool for Resource Reuse	38	a title

Chinese says as much in six characters as a Latin title says in forty. Any floor that rejects Object also rejects 智能缓存优化.

What it checks instead

A title has to look like a name:

• Latin script → more than one word
• CJK → five characters or more

Object fails the first, 智能缓存优化 passes the second, 自动化小 fails it. Whatever fails gives way to nl_summary — present on 39 of the 40 measured — cut to the same 80 characters the title was.

On reintroducing a description to the header

#8 deliberately kept the summary out of the prompt, and test/prime.test.js pinned that. This fallback is bounded to 80 characters: a name-length excerpt standing in for a name, not the 214-character median recitation #8 rejected. The full summary is still never used when a description is available, and the final fallback is the asset type.

Worth flagging for review, since it is a deliberate narrowing of an earlier decision rather than an oversight.

Tests

96/96. Four added: a one-word title stands aside, a short CJK title does not, a truncated CJK title stands aside, and an asset with neither falls back to its type. Removing the fragment check fails two of them.

Three existing assertions updated, since the fallback now names assets that previously showed only their type.

🤖 Generated with Claude Code