SFF-064: Portal repository headline

[jmrpineda]

Reported by: Codex
Requested by: jmr.pineda
Priority: P2
Affected surfaces: configuration panel, portal header
Constraints: headline must stay short enough for the portal header, must be shown below specforge.ai and the version, and must be visually truncated when needed

Summary

Add a configurable short repository headline in the configuration panel and render it in the portal header so users can quickly identify which repository a portal URL belongs to when several repositories are open at the same time.

Problem / opportunity

The current portal header does not make the repository identity obvious enough. When multiple repositories are open, users can end up looking at the correct portal URL but still not know which repository they are actually viewing.

Requested behavior

Users can define a short descriptive headline for the repository from the configuration panel. The portal shows that headline under specforge.ai and the current version so the repository can be identified at a glance. The value cannot be effectively long in the rendered header and must be truncated safely when it exceeds the available space.

Scope

• In scope: add a configuration field for the repository headline, persist it with the existing repo configuration, and render it in the portal header below the product name and version.
• Out of scope: replacing the canonical repository path, adding a long free-form description block, or redesigning the full portal header layout.

Acceptance criteria

1. The configuration panel includes a field for a short repository headline intended for portal identification.
2. The portal header renders that value below specforge.ai and the current version for the active repository.
3. Long values are visually truncated in the portal without breaking the layout.
4. When the value is empty, the portal falls back to the current behavior without visual regressions.

Notes

• This should optimize quick repo recognition when several local portals are open at once.
• The exact maximum input length can be decided during implementation, but it should be intentionally constrained rather than treated as an unlimited description field.

[jmrpineda]

Default value decision

Use a derived default value for the repository headline so the field is useful without requiring manual setup.

1. Default to the GitHub project/repository name when that metadata is available.
2. Fallback to the local directory name when GitHub metadata is not available.
3. Keep manual override support from the configuration panel.
4. Apply the same portal truncation rules to both derived defaults and custom values.

This avoids empty headers in the common case and makes the portal identifiable even before the user edits configuration.