release: 1.0.0, and record the details pane's width coupling

The 0.16.0 release was never tagged or pushed, so what it described ships
as 1.0.0 instead: the changelog section is renamed rather than followed by
an empty one, and there is no 0.16.0 for anyone to have seen.

The last remainder of the layout review's F9 goes in with it. The value
column in captionValueLayout has no minimum of its own — it takes whatever
the container leaves after the caption — and what actually keeps it
readable is the 460 px minimum on commandOutputScroll, a constant that
exists for command output being legible. The dependency was invisible at
both ends; both now state it, so lowering that width is a decision rather
than an accident. The HSplit divider is the user's side of the same thing:
it is how the value column can be widened.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/ui/jobs_view_details.go

@@ -60,6 +60,12 @@ func newDetailsPanel(firstJob job, rt *domain.JobRuntime, globalOverlapPolicy do
 	// The height here is only a floor: the scroll grows to fill whatever space the
 	// border layout gives it, so keep the minimum small so the whole window can be
 	// shrunk on short (720p) screens. Long output stays reachable by scrolling.
+	// The width, unlike the height, is load-bearing outside this widget: it is the
+	// details pane's widest minimum, so it is also what keeps the metadata value
+	// column non-empty — captionValueLayout hands the value whatever is left after
+	// the caption and has no floor of its own (see its comment in layout.go).
+	// Lowering it narrows those values with nothing to warn about it; the user can
+	// only widen them, by dragging the jobs split divider left.
 	d.commandOutputScroll.SetMinSize(fyne.NewSize(460, 70))
 	d.logs = widget.NewList(
 		func() int { return len(d.selectedLogs) },