Skip to content

SFB-069: Refinement detail properties render as block text #76

@jmrpineda

Description

@jmrpineda

Discovery date: 2026-05-27
Detected in version: 0.1.5.662
Reported by: user
Severity: medium
Environment: local SpecForge UI, refinement phase detail view
Scope / affected surface: refinement phase detail rendering, property-value presentation, operator readability
Evidence: user-provided screenshot on 2026-05-27 showing the refinement detail panel rendering property names and values as separate block lines instead of inline property rows

Summary

The refinement detail view does not present property-value data in a scannable property list. Fields that should read as inline metadata, such as Selected, Resolved, Source, Authority, Locked, and Override Allowed, are rendered as stacked block text, which makes the phase detail look broken and harder to inspect.

Expected behavior

Property-value data in the refinement detail should render as a compact list of inline rows using the format **Property**: value.

Current behavior

The UI renders each property name and its value on separate lines, producing a block-text layout instead of a structured property list. In the same panel, some trailing metadata also appears visually collapsed into raw concatenated text, which further reduces readability.

Reproduction steps

  1. Open a user story that exposes the refinement phase detail view.
  2. Navigate to the detail section that shows the harness/refinement profile metadata.
  3. Observe fields such as Selected, Resolved, Source, Authority, Locked, and Override Allowed.
  4. Notice that the view renders them as stacked text blocks instead of **Property**: value rows.

Environment details

  • Platform: local repository runtime
  • Surface: SpecForge refinement phase detail card/panel
  • Browser/runtime: unknown
  • Setup: repository local UI

Notes

  • This looks like a presentation bug, not just a styling preference, because the current output obscures the data model and makes operators parse metadata line by line.
  • The target rendering should behave more like a definition/property list than paragraph blocks.
  • Review the same renderer for other phase detail payloads so the fix does not remain refinement-specific if the rendering primitive is shared.
Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions