Repository navigation
Conversation
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>
|
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 |
|
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. |
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.5tag run:GITHUB_TOKENreports a trusted reviewer's private organization membership asCONTRIBUTOR, while an authenticated user token reportsMEMBERmain, exact reviewed commit marker on its own line, numeric comment ID, exact API/HTML URLs, trusted workflow provenance, and every successful required checkv0.17.5remains 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
CONTRIBUTORpasses while preserving all identity, PR, SHA, URL, workflow, and check requirements50c00189aca241fa3aa98c56e32309ab95bef2858edba289529ac9accaac392b,b88433b3f0185b78af987789faa0aac5ea705613381d0b293afa13bd5799d169, andb14e55738437befb0a4c98a9e85a5995e47cd40919758f68226c9fdbea04166dOSSystemExtensionsymbol; executable SHA-256 values are084c73a3de9547f7183959b918c26be1bfe0643ce11cc8ddf986eaa258bc1d31and866bcff2fd25c80847764631938fa356051926d05662e263c101fd9c8bc894b3demo.sqlite; each exact candidate PID was path-verified and stopped after capture🤖 Generated with Claude Code