fix(core): pin CorePageHeader to content size in flex-column contexts

[PierreBrisorgueil]

Summary

• CorePageHeader renders a Vuetify <v-row> which inherits flex: 1 1 auto from Vuetify internals
• When placed inside a flex-direction: column shell, the header could expand to fill all available vertical space before sibling content renders
• Adds flex: 0 0 auto on .core-page-header (the root element) to clamp it to content size; no-op in normal block flow

Test plan

• npm run lint — zero ESLint errors
• npm run test:unit — all 16 core.pageHeader.component tests pass (CSS value assertions not possible with css: false in vitest; class presence already asserted)
• Visual smoke: wrap CorePageHeader in a flex-direction:column container — header stays at ~40px content height, never balloons to fill spare space

Notes

• No unit test added for the CSS value itself — vitest.config.js sets css: false (happy-dom), making computed style assertions meaningless. This is documented in the plan.
• After merge: propagate via /update-stack to downstream Vue projects. The local guard in trawl_vue#934 (.scrap-request-shell > :deep(.core-page-header) { flex: 0 0 auto; }) becomes redundant and can be dropped.

Closes #4202

Summary by CodeRabbit

• Style
  • Improved page header layout to prevent unwanted expansion in flex containers.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f08946e1-c96e-48c6-bd4e-1374093739af

📥 Commits

Reviewing files that changed from the base of the PR and between a92952c and a60c024.

📒 Files selected for processing (1)

• src/modules/core/components/core.pageHeader.component.vue

---

Walkthrough

The page header component now explicitly sets flex: 0 0 auto on its root element, preventing the header from growing vertically when nested inside a flex-column parent container. The content container's existing flexing and truncation behavior remains unchanged.

Changes

Page Header Flex Sizing

Layer / File(s)	Summary
Flex sizing constraint for content-sized header src/modules/core/components/core.pageHeader.component.vue	Scoped CSS rule adds flex: 0 0 auto to .core-page-header to prevent vertical growth in flex-column contexts while maintaining content-sized behavior and preserving internal content container layout.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description covers the issue, solution, and test results, but does not follow the required template structure with all sections (Scope, Guardrails, etc.) filled in or explicitly marked as N/A.	Restructure the description to match the template format, including explicit Scope and Guardrails sections, even if some subsections are marked as not applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: fixing CorePageHeader to stay pinned to content size in flex-column contexts, which matches the core objective of preventing unwanted vertical growth.
Linked Issues check	✅ Passed	The PR implements the exact fix proposed in issue #4202: adding flex: 0 0 auto to .core-page-header to prevent vertical growth in flex-column contexts, with lint and unit tests passing.
Out of Scope Changes check	✅ Passed	The changes are narrowly scoped to the single CSS fix on CorePageHeader; no unrelated modifications or side effects are present beyond the stated objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/core-page-header-flex-grow

Warning

Review ran into problems

🔥 Problems

Stopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a @coderabbit review after the pipeline has finished.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR fixes CorePageHeader sizing so its Vuetify v-row root remains content-sized when used as a child inside flex-column layouts.

Changes:

• Adds flex: 0 0 auto to .core-page-header.
• Documents that this overrides Vuetify’s inherited v-row flex growth behavior.

[coderabbitai]

Actionable comments posted: 0

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.56%. Comparing base (a3207c6) to head (a60c024).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4210   +/-   ##
=======================================
  Coverage   99.56%   99.56%           
=======================================
  Files          31       31           
  Lines        1151     1151           
  Branches      329      329           
=======================================
  Hits         1146     1146           
  Misses          5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.