A feature's menu entry carries its declared summary as its title #9722

An absorbed feature's menu entry now carries its declared summary as the link's title, escaped. A summary over 200 characters is cut at a word and ends in "…". With no summary there is no title.

tsc, gate.ts, design-lint.ts and the touched suites pass (features, apps-features, features-empty, schema-migrations). The new test fails when I take out the src/web and src/actions changes and passes with them. I haven't run the full suite.

• Where the summary lives: the menu is built on every page with no git reads, and the summary is only in a repository's forge.json. So I copy it into a new nullable summary column on app_feature, the same way name and page are copied.
• When it is copied: at absorb and when an admin accepts a changed declaration. It also counts as a change, so a new summary alone waits for the admin like a rename does. The migration is 20261108180000-app-feature-summary.ts, with its pin.
• Code changes:

- MenuItem has an optional title, so other menus are unchanged. - The cut is a small new src/text/word_clip.ts, with the 200-character limit set in src/web/layout.ts. - NavFeature carries summary.

• Test: test/features.test.ts renders the menu for a feature with a summary, with none, with <script>, and with a long one. It checks escaping, no title, and the 200-character cut.

What I left out:

• Features absorbed before this migration have no summary in the menu until an admin accepts their declaration again. I did not backfill, since that would need a git read per app.
• The title shows on the user-menu link only. There is no touch-device alternative.

Closes #9681

An absorbed feature's menu entry now carries its declared summary as the link's title, escaped. A summary over 200 characters is cut at a word and ends in "…". With no summary there is no title.

tsc, gate.ts, design-lint.ts and the touched suites pass (features, apps-features, features-empty, schema-migrations). The new test fails when I take out the src/web and src/actions changes and passes with them. I haven't run the full suite.

• Where the summary lives: the menu is built on every page with no git reads, and the summary is only in a repository's forge.json. So I copy it into a new nullable summary column on app_feature, the same way name and page are copied.
• When it is copied: at absorb and when an admin accepts a changed declaration. It also counts as a change, so a new summary alone waits for the admin like a rename does. The migration is 20261108180000-app-feature-summary.ts, with its pin.
• Code changes:

- MenuItem has an optional title, so other menus are unchanged. - The cut is a small new src/text/word_clip.ts, with the 200-character limit set in src/web/layout.ts. - NavFeature carries summary.

• Test: test/features.test.ts renders the menu for a feature with a summary, with none, with <script>, and with a long one. It checks escaping, no title, and the 200-character cut.

What I left out:

• Features absorbed before this migration have no summary in the menu until an admin accepts their declaration again. I did not backfill, since that would need a git read per app.
• The title shows on the user-menu link only. There is no touch-device alternative.

An absorbed feature's menu entry now carries its declared summary as the link's title, escaped. A summary over 200 characters is cut at a word and ends in "…". With no summary there is no title.

The last check failed on the gate rule that wants a "Try:" line in a commit message. I pushed an empty commit with that line rather than amending, so history stays intact. The code is unchanged since the first push, where tsc, gate.ts, design-lint.ts and the touched suites passed. I have not seen the check pass since the Try commit. I did not rerun the tests for this push.

• Where the summary lives: the menu is built on every page with no git reads, and the summary is only in a repository's forge.json. So I copy it into a new nullable summary column on app_feature, the same way name and page are copied.
• When it is copied: at absorb and when an admin accepts a changed declaration. A new summary alone now counts as a change that waits for the admin, like a rename does. The migration is 20261108180000-app-feature-summary.ts, with its pin.
• Code changes:

- MenuItem has an optional title, so other menus are unchanged. - The cut is a small new src/text/word_clip.ts, with the 200-character limit set in src/web/layout.ts. - NavFeature carries summary.

• Test: test/features.test.ts renders the menu for a feature with a summary, with none, with <script>, and with a long one. It checks escaping, no title, and the 200-character cut. It fails without the src/web and src/actions changes.

What I left out:

• Features absorbed before this migration have no summary in the menu until an admin accepts their declaration again. I did not backfill, since that would need a git read per app.
• The title shows on the user-menu link only. There is no touch-device alternative.

Try: sign in as an admin on the preview and absorb an app whose forge.json declares a feature summary. Then open the user menu and hover its entry under "Features from apps".

An absorbed feature's menu entry now carries its declared summary as the link's title, escaped. A summary over 200 characters is cut at a word and ends in "…". With no summary there is no title.

The last check failed two tests in test/pull-quiet.test.ts, the pull page and the pull list, because each page grew about 140 bytes past its size budget. My title attribute in src/web/ui.ts left a blank line in every menu item's markup. I moved it onto the line that already holds the aria-current attribute, so the markup is as small as before. After the fix, test/pull-quiet.test.ts (4) and test/features.test.ts (25) pass and tsc is clean. I haven't rerun gate.ts, design-lint.ts or the other suites touched earlier, or the full suite.

• Where the summary lives: the menu is built on every page with no git reads, and the summary is only in a repository's forge.json. So I copy it into a new nullable summary column on app_feature, the same way name and page are copied.
• When it is copied: at absorb and when an admin accepts a changed declaration. A new summary alone now counts as a change that waits for the admin, like a rename does. The migration is 20261108180000-app-feature-summary.ts, with its pin.
• Code changes:

- MenuItem has an optional title, so other menus are unchanged. - The cut is a small new src/text/word_clip.ts, with the 200-character limit set in src/web/layout.ts. - NavFeature carries summary.

• Test: test/features.test.ts renders the menu for a feature with a summary, with none, with <script>, and with a long one. It checks escaping, no title, and the 200-character cut. It fails without the src/web and src/actions changes.

What I left out:

• Features absorbed before this migration have no summary in the menu until an admin accepts their declaration again. I did not backfill, since that would need a git read per app.
• The title shows on the user-menu link only. There is no touch-device alternative.
• A menu item marked current never shows a title. Only feature entries have one, and they are never current.

Try: sign in as an admin on the preview and absorb an app whose forge.json declares a feature summary. Then open the user menu and hover its entry under "Features from apps".

An absorbed feature's menu entry now carries its declared summary as the link's title, escaped. A summary over 200 characters is cut at a word and ends in "…". With no summary there is no title.

The tests I ran after the review changes pass (46 across six files, including word-clip, features and pull-quiet), and tsc, gate.ts and design-lint.ts are clean. I haven't rerun the rest of the suite.

What changed this round

• SUMMARY_TITLE_MAX: moved above the doc comment in src/web/layout.ts, so featureItems has its own comment again.
• Summary-only change:

- It is now a pending declaration. FeatureView.pending carries the summary, and Settings › Features shows the new menu title beside "declaration changed: review". - Accepting stores it. Before this, accepting a summary-only change was possible only through a hand-made request. - A new features.test.ts case covers it. The menu keeps the old title until accept, then shows the new one, and pending clears. - The existing pending assertion now includes the summary.

• wordClip: new test/word-clip.test.ts covers the cases below.

- Folding whitespace. - Input of exactly the limit. - A cut that lands on a space. - No space in the first characters. - A trailing parenthesis.

• Docs: docs/features/absorb.md and absorb-review.md say the summary is copied at absorb and on accept, that earlier-absorbed features show no title until re-accepted, and that the title is a pointer-only tooltip.

What I left out

• Muted second line: I did not show the summary as a muted second line in the menu item, which is the keyboard and touch answer you suggested. That changes menu markup and the pages' size budgets, so I'd do it as its own change.
• Backfill: I did not backfill earlier-absorbed features. Each one that declares a summary will show as a pending change to review once, and the docs say so.

Try: on the preview, change a feature's summary in its forge.json and open Settings › Features. You should see "declaration changed: review" with the new menu title. Accept it, then hover the entry under "Features from apps" in the user menu.