Skip to content

Verify the selector-parser backport and reconcile CSS audit evidence - #199

Merged
mvalancy merged 6 commits into
devfrom
test/css-security-backport-20261027
Oct 27, 2026
Merged

mvalancy merged 6 commits into
devfrom
test/css-security-backport-20261027

Conversation

@mvalancy

Copy link
Copy Markdown
Member

The October23 security inventory lists a vulnerable Tailwind/selector-parser chain, but current official metadata explicitly identifies the already locked parser6.1.5 as patched. This separately reviewable #186 follow-up reconciles that evidence and adds consumer regressions. It changes no dependencies, lockfile, runtime code or production/dev classification.

GHSA-rj75-hqrm-r3gf, updated2026-10-26, lists affected ranges <6.1.5 and >=7.0.0 <7.1.6, fixes6.1.5/7.1.6, and is not withdrawn. Dev 8712389 resolves Tailwind3.4.19 and postcss-nested6.2.0 to6.1.5, already present in commit 36c02c0 on October23. Fresh production audit has no CSS finding; historical observations are retained without assigning an unproved cache cause.

Four regressions check both maintained fixed branches, every locked parser path, actual Tailwind/nested resolution, flat/nested selector semantics, and generated responsive utilities. The flat input is bounded at2,048 classes; this is semantic coverage, not a timing benchmark or live-exploit claim.

Frozen head a9d66440b18a13f97daa7448b3770c9a5ce369aa: independent review, fresh clean install/build/harness/audit and exact-head CI are pending. Draft until the relevant gates and live-dev composition review pass. No Tailwind migration, threshold change or deployment. Router (#198), UUID (#196), tooling (#185) and hosted acceptance (#182) remain separate.

Canonical dated record: .agents/inbox/2026-10-27-reconcile-advisory-backports-with-locked-consumers.md; updated historical inventory: docs/quality/SECURITY_SCOPE_2026-10-23.md.

@github-actions

Copy link
Copy Markdown

🧪 Comprehensive Test Suite

  • Unit suites (Node 22.18.0 & 24.x) — core, web, server, mcp-server: ✅ passed
  • Installer & deploy config: ✅ passed

Full-stack smoke gate runs in the CI workflow.

…ckport-20261027

# Conflicts:
#	.agents/issues/INDEX.md
#	.agents/issues/security-audit-index.md
#	docs/quality/SECURITY_SCOPE_2026-10-23.md
@mvalancy
mvalancy changed the base branch from dev to fix/router-security-20261027 October 27, 2026 21:13
@github-actions

Copy link
Copy Markdown

🧪 Comprehensive Test Suite

  • Unit suites (Node 22.18.0 & 24.x) — core, web, server, mcp-server: ✅ passed
  • Installer & deploy config: ✅ passed

Full-stack smoke gate runs in the CI workflow.

@mvalancy

Copy link
Copy Markdown
Member Author

Stacked composition head f08077fb37c4e42c0e4af7679aa0c0f31447357b includes reviewed Router #198, focus #201 and merged UUID #196. The PR temporarily targets #198 to keep its displayed diff scoped. Independent exact-head review verified exactly the original five CSS test/document paths differ from Router 14a4fcc; every other tracked file is identical. Both index rows and security inventory sections were retained during conflict resolution. No findings.

Fresh clean install, all four package builds and 176 harness cases passed. Fresh-cache production audit reports zero vulnerabilities on this composed lock; tooling advisories remain separate in #185. That audit result is not an exploit or hosted-readiness claim. Exact-head CI 40584887636 and Comprehensive 40584887458 are pending. Older in-progress CI was superseded, not counted as green. Integration order remains #201 → #198 → #199 with live-base/tree verification before each dev merge.

@github-actions

Copy link
Copy Markdown

🧪 Comprehensive Test Suite

  • Unit suites (Node 22.18.0 & 24.x) — core, web, server, mcp-server: ✅ passed
  • Installer & deploy config: ✅ passed

Full-stack smoke gate runs in the CI workflow.

…urity-backport-20261027

# Conflicts:
#	.agents/issues/INDEX.md
@mvalancy
mvalancy changed the base branch from fix/router-security-20261027 to fix/fixture-git-maintenance-20261027 October 27, 2026 22:01
@github-actions

Copy link
Copy Markdown

🧪 Comprehensive Test Suite

  • Unit suites (Node 22.18.0 & 24.x) — core, web, server, mcp-server: ✅ passed
  • Installer & deploy config: ✅ passed

Full-stack smoke gate runs in the CI workflow.

…-security-backport-20261027

# Conflicts:
#	.agents/issues/INDEX.md
@mvalancy
mvalancy changed the base branch from fix/fixture-git-maintenance-20261027 to fix/lod-transition-ownership-20261027 October 27, 2026 22:44
@github-actions

Copy link
Copy Markdown

🧪 Comprehensive Test Suite

  • Unit suites (Node 22.18.0 & 24.x) — core, web, server, mcp-server: ✅ passed
  • Installer & deploy config: ✅ passed

Full-stack smoke gate runs in the CI workflow.

@mvalancy

Copy link
Copy Markdown
Member Author

Imported reviewed LOD correction #207 without changing this feature's own implementation. The composition adds exactly four reviewed paths (renderer effect, regression, lesson and index); independent review verified complete tree/blob unions, parents and unchanged feature code. Source #207 passes LOD desktop/phone2/2, web346/346, harness175/175, smoke6/6, build/types/lint. Refreshed exact-head CI is active; earlier failures/cancelled superseded runs are retained and are not passes. The CSS acceptance failure is addressed by the isolated transition-ownership fix, not by retries or relaxed assertions.

…curity-backport-20261027

# Conflicts:
#	.agents/issues/INDEX.md
@mvalancy
mvalancy changed the base branch from fix/lod-transition-ownership-20261027 to test/motion-camera-readiness-20261027 October 27, 2026 23:30
@github-actions

Copy link
Copy Markdown

🧪 Comprehensive Test Suite

  • Unit suites (Node 22.18.0 & 24.x) — core, web, server, mcp-server: ✅ passed
  • Installer & deploy config: ✅ passed

Full-stack smoke gate runs in the CI workflow.

@mvalancy

Copy link
Copy Markdown
Member Author

Final correction composition is now 0157bd04d169dab7be323f13c7a4d2a058c8c697. Independent review verified the complete six-path import from reviewed LOD/camera-readiness head 7cbf292: source renderer, both browser regressions and lessons match byte-for-byte; feature-specific code and dependencies remain unchanged. The symptom index retains every previous row and adds the motion lesson. No instruction or authority changes.

The combined local motion suite passes 3/3 in 2.1 minutes with zero retries; combined LOD validation and fresh exact-head CI remain pending. Previous green heads do not establish this composition's final acceptance. Earlier LOD/rotation failures and insufficient title-geometry evidence remain retained. Integration follows #207 → #210 → #199 → #195 → #197 → #202 → #206 → #211, with native dev merge verification and post-merge CI before issue closeout. Independent agent review is not a GitHub non-author approval.

@mvalancy

Copy link
Copy Markdown
Member Author

Final native dev integration preflight: source 0157bd04d169dab7be323f13c7a4d2a058c8c697; live dev 6136731acf6c4f7da222b93279122b11aedf79e3, whose complete tree equals reviewed motion base 7cbf292. The five-path CSS-only test/documentation delta remains independently reviewed; parser6.1.5 was already patched, so this verifies consumers and reconciles historical evidence without changing runtime dependencies. Expected resulting tree: dae70f5669333c3a3baf7adaff723b0c6a47fc6a.

CI40602587630 and Comprehensive40602587639 passed every applicable job. Strict downloaded artifacts contain smoke6, new-user42, LOD2, routes7, mobile27 and performance3; all passed with zero warnings/skips/evidence errors/timeouts/nonzero executions. Effects and showcase also passed. The production-main/nightly job is inapplicable here.

Earlier pre-correction LOD failure40591493014 remains retained. Retargeting to dev preserves the exact reviewed content. Native admin integration uses the owner's standing dev-only authority; no non-author GitHub approval is claimed. Open incident/remediation issues stay open until post-integration dev CI passes. No main, release, deployment or protection changes are included.

@mvalancy
mvalancy merged commit 408857a into dev Oct 27, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant