MWPW-204282: Fix broken status filter in M@S Studio

[Axelcureno]

Resolves https://jira.corp.adobe.com/browse/MWPW-204282

The Fragments table Status filter queried the mas:status/* AEM tag, while the Status column shows the fragment's real publication state. Those had fully diverged: of 300 sandbox fragments, zero carried mas:status/published while 50 were genuinely PUBLISHED. Selecting Published returned Draft and Modified cards.

A partial bridge existed in mas-repository.js (translating the published tag into filter.status), but the in-memory cache-narrowing path bypassed it, so the filter also worked on a cold search and then silently returned stale results once cached.

• Status filters on real publication state, server-side via filter.status
• Options go from 3 to 5: Published, Draft, New, Modified, Unpublished (multi-select)
• AEM.searchFragment takes an array; the API accepts multiple values and NEW/MODIFIED/UNPUBLISHED are all queryable
• Store.filters.status is normalized and whitelisted, so an invalid value degrades to no filter
• Status now participates in the cache key, the narrowing test, and the in-memory filter. Narrowing treats adding a status as widening and forces a refetch, which is the half of the bug unit tests caught red-to-green
• Legacy mas:status/published special case deleted

Measured against the live API: no rarity penalty. NEW (1 in 300 fragments) is as fast as an unfiltered query.

Not done: manual browser QA. Reviewer check is to open the Status picker, tick Draft, then also tick New and confirm the result set widens.

• C1. Cover code with Unit Tests
• C2. Add a Nala test - none exists for the filter panel; needs a call from #fishbags
• C3. Verify all Checks are green
• C4. PR description contains working Test Page link
• C5. Ready to demo from Test Page
• C6. Re-read Jira and validated ACs

Test URLs:

• Before: https://main--mas--adobecom.aem.live/
• After: https://mwpw-204282--mas--adobecom.aem.live/

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

• Re-sync branch

Commits

• 2e0b174 ✅ (latest)
• 350cc28 ✅
• 23ff9ca ✅
• 7098ded ✅
• c207ef8 ✅
• 379aa5d ✅
• c2f8450 ✅
• 93ea9f1 ✅
• b3e24d7 ✅
• 245e065 ✅
• 6e68f04 ❌
• f3a98bf ❌
• 1bfe2ed ❌
• 032ebf0 ❌
• 1a46f2e ❌
• 26d0e88 ❌
• 8eaa8c3 ❌
• d91b021 ❌
• 8d28297 ❌
• 750ee0c ❌
• 58ca0ce ❌
• 5d6975e ❌
• 3d9ca85 ❌
• 9985940 ❌
• 7c02580 ❌
• 67357ca ❌
• c230d4a ❌
• b1de5ad ❌
• aac5a08 ❌
• 6f9dbec ❌

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.75%. Comparing base (2f2e131) to head (a370d87).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1165      +/-   ##
==========================================
+ Coverage   90.71%   90.75%   +0.03%     
==========================================
  Files         318      318              
  Lines      101712   101814     +102     
==========================================
+ Hits        92271    92401     +130     
+ Misses       9441     9413      -28     

Files with missing lines	Coverage Δ
studio/src/aem/aem.js	52.35% <100.00%> (+0.16%)	⬆️
studio/src/aem/mas-filter-panel.js	91.45% <100.00%> (+1.00%)	⬆️
studio/src/mas-repository.js	81.29% <100.00%> (+0.24%)	⬆️
studio/src/router.js	88.68% <100.00%> (ø)
studio/src/store.js	96.59% <100.00%> (+0.13%)	⬆️

... and 7 files with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2f2e131...a370d87. Read the comment docs.

🚀 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.

[Axelcureno]

@honstar Added status to the filters hash link, so it round-trips like the other filters now. filtersValidator already sanitizes it, so a hand-edited #status=BOGUS gets dropped.

Also added it to the promotions editor ignorable set, so toggling status there does not trigger the discard prompt.

5 new tests in router.test.js. Full studio suite: 3751 passed, 0 failed.

[Axelcureno]

@Andrei4226 I think this landed on the wrong PR. This one only touches the Studio status filter (store.js, router.js, mas-repository.js, mas-filter-panel.js), there are no ost-search.js changes here.

The resolveOsi/resolveOfferId race and the stale this.query point look like they were meant for #1157, which you approved this morning. Mind dismissing the changes-requested here? Happy to take those two in #1157 or a follow-up ticket.

[Andrei4226]

@Andrei4226 I think this landed on the wrong PR. This one only touches the Studio status filter (store.js, router.js, mas-repository.js, mas-filter-panel.js), there are no ost-search.js changes here.

The resolveOsi/resolveOfferId race and the stale this.query point look like they were meant for #1157, which you approved this morning. Mind dismissing the changes-requested here? Happy to take those two in #1157 or a follow-up ticket.

Sorry @Axelcureno, you're right, this is the wrong PR.
Dismissing the requested changes here.
I will move my review to #1157 as a comment (or a follow-up ticket if you'd rather track it separately, no problem).

[Andrei4226]

LGTM
Nit: I saw that the Status filter has a grey background, unlike the others (it's white in main). Also, I think the chevron should be on the right side, like the other filters in main (just for consistency) and the alignment as well.

[honstar]

Nit: this is unused and can be removed as well.