Skip to content

Flowlight 0.17.6 — corrected consolidated release - #85

Closed
blessdyb wants to merge 7 commits into
mainfrom
release/0.17.6
Closed

blessdyb wants to merge 7 commits into
mainfrom
release/0.17.6

Conversation

@blessdyb

@blessdyb blessdyb commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Flowlight 0.17.6 is the corrected public patch for the consolidated 0.17.x redesign. It carries the complete reviewed 0.17.5 product tree forward unchanged and repairs the release-evidence authorization boundary exposed by the immutable v0.17.5 tag run:

  • GitHub's release GITHUB_TOKEN reports a trusted reviewer's private organization membership as CONTRIBUTOR, while an authenticated user token reports MEMBER
  • the explicit trusted-reviewer login allowlist is now authoritative instead of the viewer-dependent association label
  • review evidence still requires the exact allowlisted GitHub account, exact PR targeting main, exact reviewed commit marker on its own line, numeric comment ID, exact API/HTML URLs, trusted workflow provenance, and every successful required check
  • the association label remains recorded in the provenance manifest for auditability
  • all consolidated AI Agents, Alerts, Policies, Sources, Live accessibility, plugin/provider, performance, CI-reuse, Pages, CodeQL, and single-signing changes remain unchanged

v0.17.5 remains immutable and unpublished. Both preparation attempts stopped at the review-evidence preflight before Xcode selection, certificate import, signing, notarization, artifact creation, or publication. Store metadata, upload, build selection, and submission remain deferred to 0.18.0.

Verification

  • 1,218 native tests passed with zero failures and no first-party Swift warnings
  • 90 Python classifier/release/palette/artifact/workflow/site tests passed
  • 17 focused release-evidence tests passed
  • a real exact-head fixture with the trusted reviewer reported as CONTRIBUTOR passes while preserving all identity, PR, SHA, URL, workflow, and check requirements
  • the new regression test was proved fail-capable: restoring the old association filter reproduces the exact missing-review and missing-check failures, then passes after the deliberate regression is removed
  • Xcode project drift, 53-page static site, CodeQL gate, notarization, rule-pack policy, Homebrew updater, chart palette, localization property lists, and whitespace gates pass
  • the exact signed Developer product is 0.17.6 (80), with the independently versioned 0.16.3 (28) system extension; the app, extension, and response-script helper are universal, satisfy their designated requirements, and are byte-identical between archive and export
  • fresh Developer executable SHA-256 values are 50c00189aca241fa3aa98c56e32309ab95bef2858edba289529ac9accaac392b, b88433b3f0185b78af987789faa0aac5ea705613381d0b293afa13bd5799d169, and b14e55738437befb0a4c98a9e85a5995e47cd40919758f68226c9fdbea04166d
  • the exact unsigned Store graph is app and app extension 0.17.6 (80), universal, and contains no Developer system extension, response-script helper, privileged installer, SystemExtensions framework linkage, or OSSystemExtension symbol; executable SHA-256 values are 084c73a3de9547f7183959b918c26be1bfe0643ce11cc8ddf986eaa258bc1d31 and 866bcff2fd25c80847764631938fa356051926d05662e263c101fd9c8bc894b3
  • real-machine acceptance passed for Live, AI Agents, and Connections at 1000 × 660 using only synthetic demo.sqlite; each exact candidate PID was path-verified and stopped after capture
  • independent security review found no verified HIGH or MEDIUM authorization bypass in the correction

🤖 Generated with Claude Code

blessdyb and others added 7 commits November 4, 2026 22:18
Unify policy inventory and activity, reshape Sources into one operational page, fix History hover dismissal, and harden exact-byte release preparation with authenticated review provenance.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Keep trusted reviewer configuration and exact review markers out of release-check diagnostics while preserving actionable fixed-category errors.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Consolidate the completed unpublished 0.17.4 work and all remaining approved 0.17.x redesign scope into one public release. Add explainable agent inventory, durable alert triage, Inspect-owned provider profiles, accessible Live inspection, measured performance gates, and hardened CI, Pages, CodeQL, and signed-release provenance.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Consolidate the remaining 0.17.x product redesign into the AI-agent inventory, unified policy activity, durable alert triage, responsive native layouts, and runtime-effective provider profiles. Keep merged agent identities consistent across reporting and enforcement, preserve truthful inspection-effect provenance, and make migrations interruption-safe.

Harden CI reuse, CodeQL gating, exact-artifact Pages deployment, signed preparation, and credential-free publication. Add fail-capable migration, policy, plugin transport, activity, accessibility, performance, and product-separation coverage.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Preserve identity ordering while replacing chained array concatenation with explicit append operations so the prospective-merge build compiles within the CI Swift frontend type-check budget.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Preserve exact segment clipping while rejecting impossible card intersections by inclusive segment bounds, and reuse placement collision state instead of rebuilding it for every node. Keep the 600-edge layout inside its fail-capable CI budget.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Carry the consolidated 0.17.x product forward after the immutable 0.17.5 tag exposed viewer-dependent GitHub reviewer association metadata. Trust the configured reviewer allowlist while preserving exact comment, pull request, commit, workflow, and check provenance, then bump and regenerate the corrected release metadata.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@blessdyb

blessdyb commented Nov 5, 2026

Copy link
Copy Markdown
Contributor Author

Independent security and release-correctness review completed against the exact committed correction. The configured reviewer login allowlist remains the authorization boundary; GitHub-authenticated login, exact PR/SHA marker, numeric comment ID, exact API/HTML URLs, trusted workflow provenance, linked pull request, and successful required checks remain enforced. The viewer-dependent association label is retained as evidence only. No verified HIGH or MEDIUM blocker survived at 9/10 confidence.

Reviewed-Commit: 3bd9387

@blessdyb

blessdyb commented Nov 5, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #86 after immutable v0.17.6 completed signing and Apple notarization but failed before artifact retention when Apple CloudKit ticket delivery lost the connection during DMG stapling. v0.17.6 remains unpublished and untouched.

@blessdyb blessdyb closed this Nov 5, 2026

This branch had an error being deployed

1 failed deployment
release — 3bd93873 Deployed Nov 5, 2026 by blessdyb via Prepare signed release #219
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