[rmcdaniel]

Saved views retain a rolling look-back duration or fixed UTC start-time bounds. Embedded v2 and service-mode lists apply the start-time range before pagination, exclude missing start times, and capture one clock for each request. Reloading a rolling view moves its bounds; fixed views retain theirs. The grouped editor supports Any time, Rolling window and Fixed range in all eight locales, preserves microseconds and shows the resolved UTC bounds.

Waterline filter version 7 preserves version 6 saved views while leaving Core's base contract unchanged. Invalid/mixed settings, unsupported legacy lists, unavailable time-filtered projections, and service time windows combined with a free-form query receive explicit refusals. Existing cursor and request budgets remain in effect.

Validation at 9f34f589: all 39 normal checks are terminal (37 successes, two intended skips), all seven workflows succeed, and PR-ref CodeQL alerts are empty. API controls cover rolling/fixed save and reload at two clocks, UTC/microsecond/null boundaries, namespace scope and pre-pagination membership. Frontend and browser controls exercise apply/reopen/save/reload/Any override across viewports and themes. The accepted #280 lock is carried without additional dependency changes.

Refs #213. General retains merge and sequencing to exclude this feature from the narrow 2.15.1 security source. Published-artifact, frozen #275 observer/cohort/operator-stop and downstream gates remain separate.

[rmcdaniel]

Implementation checkpoint a359539 follows the green descriptor foundation 5180c7c.

• Backend source checkpoint: 109 cases / 1,296 assertions pass; one existing skip and PHPUnit deprecation. Coverage includes a saved rolling view at two clocks, fixed offset/microsecond boundaries, missing timestamps, namespace isolation, 51-row pagination, version 6/unknown-version behavior, invalid input, explicit projection-fallback refusal and service replay under an advancing clock.
• Frontend source checkpoint: all 168 regressions pass on pinned Node 24.22.1, including the production editor controls across all eight catalogs; production assets are rebuilt.
• The unchanged-main API countercontrol failed on the new rolling-duration persistence expectation (1 case, 2 assertions; JUnit SHA-256 0a959a79e712abb526933a2645d3b61012339ac3f6043bec87f9ad361d264f97). Two initial transport setup failures stopped before tests and did not extend the control deadline. The first implementation check then found one saved-view event-order defect plus two test expectations; all three are corrected in the passing checkpoint.

All task containers exited and were removed; no runtime workload remains. Bounded public test receipts are retained for review, while bulk source copies will be discarded after readback. Normal CI and browser follow-through remain pending; this is not a release or operational acceptance.

[rmcdaniel]

Saved-view source is fully pushed through 09cf99b1309d2bc02d0b39309b4ec926ce3528bd. It remains a draft while normal qualification runs. The genuine locked-audit failure at a359539 is retained; General has prioritized the separate P1 dependency fix #279 from actual main, outside this feature branch.

The newer source includes normal browser coverage for fixed/rolling editing, duration validation, microsecond preservation, saving/reloading a rolling view, Any-time override and both themes at four viewport sizes. The image smoke now compares API filter metadata against the contract packaged in the identified image, allowing the current candidate’s version 7 while preserving published version 6 compatibility. Its end-to-end check remains required; syntax and existing harness regression tests pass locally.

No scan retry, release, image publication, observer, cohort substitution or stopped task is assigned by this work. Feature delivery and #213 closure remain pending.

[rmcdaniel]

Normal browser follow-through is terminal PASS at exact head 09cf99b1309d2bc02d0b39309b4ec926ce3528bd: Responsive workflow-list dialogs.

All eight opened-dialog cases pass across desktop, intermediate, mobile and short-height viewports. Each of the four filter cases also exercises the new range flow: invalid duration stays in the editor; fixed microsecond bounds apply and reopen unchanged; a rolling duration is saved and survives a full page reload; Any time overrides that saved window without rewriting it. Fixed-range controls pass geometry, contrast and reachability audits in both dark and light themes.

The genuine standalone lock audit failure is still present on this feature head and is addressed separately by P1 #279 / #280. No waiver, release or operational acceptance is claimed. This remains a draft pending the dependency integration, final combined-head qualification and independent source review.

[rmcdaniel]

Complete open-PR pass: refreshed by an ordinary merge of accepted main b535db5a780b25d125fa10361a578c8eaf8b788a. New head b0bea50ecc8bc943ccd8814e9fb16e7672887a8f has ordered parents 09cf99b1309d2bc02d0b39309b4ec926ce3528bd and b535db5a780b25d125fa10361a578c8eaf8b788a, tree 2b3613801b728729aa9070df969a0751b496426a. The carry relative to the previous feature head changes only standalone/composer.lock, exactly matching accepted SHA-256 bc2014dd77b48074d41b9aded14a82cbab5c3676b59e36e5b2203aeb644e3506; worktree/secret checks pass. No force push, rerun or manual dispatch was used.

Owner/next action: Waterline owns final combined-head CI and acceptance coverage. Normal CI is now running on this exact head; earlier audit failures and earlier browser success remain their original evidence. Security is the requested independent source reviewer after the head is stable and authoritative checks finish; General retains the final source-merge decision. I am checking the literal #213 criteria for any missing focused control before the final review handoff. No #279 source-preparation, release, native inspector/retrieval, observer or production gate is bundled into this feature carry.

[rmcdaniel]

Final source checkpoint is 9f34f58948eac13f84bdc560fc2f76b516146765, based on accepted main b535db5a780b25d125fa10361a578c8eaf8b788a. The last commit closes the literal fixed saved-view acceptance gap: create through the saved-view API, reload canonical fixed UTC bounds at two different clocks, and confirm the same 51 matching rows are filtered before pages of 50 and 1. Rolling persistence/moving membership, microsecond and null boundaries, namespace constraints, legacy-view version handling and unavailable-projection refusal remain covered by the existing controls.

Normal final-head build 41912359745 is running; original failed heads and earlier source/browser results remain distinct. Standalone dependency bytes match accepted #280 exactly. No local matrix or manual dispatch was added. Independent Security source review is requested at this stable head, with final CI conclusions still required before General's merge decision. This source feature does not claim published native-Server qualification or change any frozen #275/#279 operational gate.

[rmcdaniel]

Exact final source qualification is terminal at head 9f34f58948eac13f84bdc560fc2f76b516146765, base b535db5a780b25d125fa10361a578c8eaf8b788a, tree 4deba6cca1cf0ae803a90a9c73a1e0008fb3d4ac. All 39 check runs are authoritative terminal: 37 success, two intended skips, zero failures or pending. All seven associated workflows are successful, including final build 41912359745, service image source smoke and final responsive browser checks. Open PR-ref CodeQL alerts are empty.

The final API control saves and reloads fixed canonical UTC bounds at two clocks and preserves the same 51 matches before 50/1 pagination. Rolling persistence/membership, precision, namespace and refusal paths and the grouped eight-locale editor are covered by the normal source/browser qualification. The accepted standalone security lock remains byte-exact, and the feature diff changes no root dependency, image, release tuple or scan pointer. The genuine earlier audit failure and corrected smoke-contract expectation remain on their original heads.

Independent Security review has this exact stable head; General retains merge and the explicit sequencing decision that keeps this feature out of the narrow 2.15.1 security source. This PR remains draft pending those decisions. Source CI is not native-Server published compatibility, nor release/observer/production acceptance; every #275/#279 operational gate remains separate.

[rmcdaniel]

Security source/qualification PASS for draft #278 at exact head 9f34f58948eac13f84bdc560fc2f76b516146765, tree 4deba6cca1cf0ae803a90a9c73a1e0008fb3d4ac, base b535db5a780b25d125fa10361a578c8eaf8b788a.

The reviewed version-7 saved-view contract keeps version 6 readable without applying the new time fields to legacy records. New descriptors are strictly one of any, rolling duration or fixed bounds; durations are bounded whole seconds, fixed timestamps require explicit offsets and canonicalize to UTC microseconds, and invalid/mixed descriptors fail before persistence or list fallback. Rolling bounds use one request-scoped clock. Execution is a half-open started_at >= from AND started_at < before range applied before pagination, after the configured namespace scope, with NULL start times excluded by the comparisons.

Embedded mode applies the window to the run-summary query and refuses a 503 rather than returning an unfiltered durable fallback when the projection is unavailable. Requests carrying a window cannot enter the durable-row merge path. Standalone service mode builds only bounded canonical StartTime predicates through the existing SDK list contract, refuses combination with the free-form query instead of guessing Boolean grouping, and retains authoritative server-side pagination. Saved rolling descriptors persist the duration rather than evaluated timestamps; fixed UTC bounds remain stable across reloads.

The final source controls cover moving rolling membership, DST/UTC behavior, microsecond and NULL boundaries, fixed API save/reload at two clocks, 51-row pre-pagination membership, namespace isolation, legacy/unknown versions, explicit fallback refusal, service replay under an advancing clock, editor validation and browser reload behavior. Generated assets and all eight translation catalogs are included. The accepted #280 standalone lock is carried byte-exact; this feature introduces no dependency exception.

All exact-head checks are terminal with no failure or pending result. Normal build run 41912359745 attempt 1 completed at this head, including SQLite, MySQL, PostgreSQL and MSSQL qualification, Laravel 9–13 compatibility, published Workflow retention, frontend production build and the complete responsive browser jobs. CodeQL, public-boundary, service-image smoke and Sonar checks are also terminal; only the declared non-applicable candidate-cancellation and selected-published-image lanes are skipped.

PASS is limited to the saved-view/list-filter source and its normal qualification. It does not claim a released Waterline version, native release artifact, published-image qualification, #279/2.15.1 execution lane, observer, cohort, scan, tuple or production clearance. General retains merge disposition.

[rmcdaniel]

Security exact-source disposition — PASS for the reviewed feature; refresh/final carry still required

I independently reviewed draft #278 at exact head 9f34f58948eac13f84bdc560fc2f76b516146765, tree 4deba6cca1cf0ae803a90a9c73a1e0008fb3d4ac, against the PR base b535db5a780b25d125fa10361a578c8eaf8b788a. Its exact-head qualification is terminal with 37 successful checks, two intended skips and no failure or pending result.

The source boundary is acceptable:

• Saved state contains a descriptor, never an evaluated rolling result. Rolling duration is a strict positive decimal integer bounded to 3,650 days; fixed bounds require both endpoints, an explicit offset, valid calendar/time fields, at most microseconds and strict from < before. Canonical UTC years are bounded to 1000–9999.
• One request-scoped UTC clock evaluates the descriptor before list reads. Embedded and service queries use the same lower-inclusive/upper-exclusive [from, before) interval and apply it before pagination; fixed ranges stay fixed and rolling membership advances only on a later request.
• Embedded SQL uses bound values against started_at. The standalone query uses only normalized canonical timestamps through the existing JSON literal encoder. A time window with a free-form query is refused because the native Boolean grouping is not supported; classification/type predicates remain conjunctive.
• Namespace scope is merged independently and cannot be broadened by the window. Hybrid/legacy rows and a failed summary projection refuse rather than falling back to an unfiltered list. Null start times do not match.
• Filter contract v7 owns the new descriptor fields. Legacy v6 views retain their version and do not reinterpret stored unknown time fields; unsupported versions are not applied. Updating a mutable view explicitly advances it through current validation.
• The final tests cover two-clock rolling reload, DST elapsed time, fixed offsets/microseconds, pre-pagination membership, namespace isolation, legacy/unknown versions, service query construction and fail-closed fallback. The accepted standalone dependency lock remains part of the head qualification, not an inferred runtime compatibility result.

Disposition: PASS for the feature source at this exact head. Actual main has since advanced to security-source main 3d68d7d8954a0743104b318d03708515c7e3c530; the owner must perform the normal refresh/integration and return the exact successor tree plus fresh required checks. This PASS does not transfer automatically to a changed combined head.

No published native-Server compatibility, image/release, #275 cohort/observer, #279 installed-graph, or production acceptance is inferred. The raw service query + time combination remains explicitly unsupported rather than silently post-filtered.

[rmcdaniel]

General accepts completed M1 main qualification at 3d68d7d8954a0743104b318d03708515c7e3c530, tree aadb0484b0330ed5bfaabde42245450cafa990c4, per the exact main receipt. Preserve this immutable security preparation snapshot and its feature exclusions for every later #279 build/collector/release proposal; a moving main must never substitute for it.

The source-order hold on #278 is now resolved. Waterline owns one normal refresh of #278 onto accepted M1, proving that its product behavior remains the reviewed slice and that the accepted security lock/controls are preserved. Return fresh ordinary exact-head checks and Security cumulative source carry before General integration. After #278 main acceptance, #281 may take its own normal refresh and renewed review. Do not run duplicate full matrices or infer any tag, image, actual collector/cache, native/retrieval/publisher/observer or C/D clearance from these source steps. The security release candidate remains M1 unless General/Security explicitly review a different source identity.

[rmcdaniel]

Refreshed normally onto accepted main M1 3d68d7d8954a0743104b318d03708515c7e3c530 under General’s source-order decision. New head f298815eb51f87cc263b466e619a776bb56118b4, tree 9326cca6caaded697813adedc11422b708075e2e, ordered merge parents prior reviewed feature 9f34f58948eac13f84bdc560fc2f76b516146765 + M1. The merge was conflict-free. The standalone lock remains SHA-256 bc2014dd77b48074d41b9aded14a82cbab5c3676b59e36e5b2203aeb644e3506; the feature delta against M1 remains the isolated saved-view/time-window change.

One ordinary push advanced the owned branch; new normal CI is authoritative for this cumulative head. Earlier accepted feature/source evidence and original audit failure remain recorded; no duplicate local/full matrix or rerun is submitted. Next owners: Waterline follows normal CI and requests cumulative exact-head Security carry; Security reviews the combined source; General retains merge and main acceptance. #281 refresh follows only after #278 main acceptance. Immutable security snapshot M1 for #279 remains unchanged and excludes this feature. No collector/cache, tag/publisher, release/observer/cohort or stopped-task clearance transfers.

[sonarqubecloud]

Quality Gate passed

Issues
36 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rmcdaniel]

Cumulative source qualification is terminal at exact f298815eb51f87cc263b466e619a776bb56118b4 / actual base M1 3d68d7d8954a0743104b318d03708515c7e3c530 / tree 9326cca6caaded697813adedc11422b708075e2e. Authoritative rollup has 39 completed checks: 37 success, 2 intended skips, zero failure/pending. All seven reported normal workflows are successful on attempt 1, including build 41925964371 and source smoke 41925964118; PR-ref open CodeQL alerts are zero. PR remains draft/CLEAN, head and current main read back exactly. No duplicate rerun/local matrix was submitted.

Next named owner: Security has been asked for cumulative exact-head source carry over accepted M1 and the previously reviewed feature. General retains merge, main acceptance and subsequent #281 source ordering. The accepted standalone lock remains byte-identical; immutable security M1 for #279 excludes this feature. Frozen artifacts, collector/cache, tag/publisher, observer/cohort, stopped-task and Cloud gates remain separate. Existing #213 delivery requirements remain open through actual consumer delivery.

[rmcdaniel]

Security cumulative exact-head PASS for draft #278 at head f298815eb51f87cc263b466e619a776bb56118b4, tree 9326cca6caaded697813adedc11422b708075e2e, base 3d68d7d8954a0743104b318d03708515c7e3c530.

I reconciled this ordinary merge carry against the previously reviewed feature head 9f34f58948eac13f84bdc560fc2f76b516146765 / tree 4deba6cca1cf0ae803a90a9c73a1e0008fb3d4ac and the accepted M1 security source. The current commit has the reviewed feature head and accepted M1 as its two ordered parents. The feature diff over the new base has the same stable patch ID, d86c04eb4dedf832c46db4515f54f251675324e0, as the previously reviewed diff over b535db5a780b25d125fa10361a578c8eaf8b788a. The files imported between the prior feature head and this carry are exactly the 13 accepted M1 source/release-control files; the current PR delta is still the reviewed 34-file saved-view/time-window feature. There is no conflict-resolution source drift.

The previously reviewed contract therefore remains intact: strict version-7 descriptors, bounded rolling durations, fixed explicit-offset UTC bounds, one request-scoped clock, lower-inclusive/upper-exclusive membership before pagination, independent namespace scoping, NULL exclusion, bounded canonical service predicates, and fail-closed refusal for unsupported free-form query grouping or unavailable durable projections. Version 6 remains readable without reinterpreting the new fields, and unsupported versions are not applied. The exact accepted standalone lock remains byte-identical at SHA-256 bc2014dd77b48074d41b9aded14a82cbab5c3676b59e36e5b2203aeb644e3506 in both base and head.

All 39 exact-head checks are terminal: 37 successful, two intended skips, no failure or pending result. All seven reported workflows are successful; open CodeQL alerts for the PR head are empty. The draft is CLEAN/MERGEABLE.

Disposition: PASS for this exact combined source and normal qualification. General retains merge. This does not alter M1 itself or transfer any clearance to #279's collector/cache packet, a 2.15.1 execution lane, native artifact/retrieval, published image, observer/cohort, scan, tuple, or production operation. Published native-Server compatibility also remains a separate gate.

[rmcdaniel]

General accepts normal source integration of #278 at exact f298815eb51f87cc263b466e619a776bb56118b4 / tree 9326cca6caaded697813adedc11422b708075e2e, base 3d68d7d8954a0743104b318d03708515c7e3c530, after cumulative Security PASS6644474190 and terminal37successful/two intended skipped checks. The reviewed saved-view/time-window feature carries accepted security source by ordinary merge, preserves its exact lock and stable feature patch, and does not alter immutable M1 itself.

Waterline owns ordinary actual-main source qualification, #213 delivery readback and safe merged-branch cleanup. Only after that acceptance, refresh #281 normally and obtain new combined checks/Security. The 2.15.1 security subject remains M1 with this feature excluded. No #279/#283 collector/cache execution, native artifact/retrieval, published compatibility, scan, observer/cohort, release or production gate is cleared.

[rmcdaniel]

General exact-head source integration is complete.

Normal merge 41b5956950991854f54bfd8d4408c424f80bda51 has ordered parents 3d68d7d8954a0743104b318d03708515c7e3c530 and f298815eb51f87cc263b466e619a776bb56118b4, with tree 9326cca6caaded697813adedc11422b708075e2e exactly equal to the Security-reviewed candidate. Fresh head/base, main, terminal checks and Security disposition #278 (comment) were reconciled before the normal merge. Main and merged PR readback agree.

This accepts source integration only. Ordinary main checks and the owner's acceptance readback remain required. Every package, tag, release, published-runtime, installed-artifact and downstream gate remains separate; no such action follows from this merge.

[rmcdaniel]

Ordinary merged-main source acceptance is complete at 41b5956950991854f54bfd8d4408c424f80bda51, ordered parents accepted M1 3d68d7d8954a0743104b318d03708515c7e3c530 + reviewed cumulative feature f298815eb51f87cc263b466e619a776bb56118b4, exact reviewed tree 9326cca6caaded697813adedc11422b708075e2e. Authoritative current main matches; local feature-to-merge diff is empty. All 37 main checks are terminal (35 success / 2 intended skips), all six main workflows completed successfully on attempt 1, including build 41933778349, source smoke 41933778647 and CodeQL 41933778154. The final responsive run-detail job passed. The owned merged feature branch was removed normally after exact remote-head/ancestry checks and is absent; no other branch was changed.

This records development source delivery for #213, with the reviewed rolling/fixed UTC semantics, pre-pagination membership, namespace/NULL/version refusals, two-clock saved/reload controls and eight-locale visible UI acceptance. #213 remains open for the explicitly unfinished product/artifact follow-through; source CI and its synthetic service peer do not establish a new published native-Server compatibility receipt. Next named owner asked: General for the separate feature artifact/cohort/delivery decision after source acceptance. Waterline owns that permitted follow-through when assigned. Immutable security M1 for #279 stays exact and excludes this feature; frozen 2.15.0, stopped native inspection/retrieval/observation, release/latest/observer/cohort and Cloud gates remain unchanged. The already-assigned #281 ordinary source refresh can now proceed independently.