feat(hub): єдиний JSON бекап, овервью Фініка (смуги 50/75%, ліміти ли…#45
Merged
Conversation
…ше >60%) Made-with: Cursor
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced May 4, 2026
Skords-01
added a commit
that referenced
this pull request
May 6, 2026
Closes pr-plan-2026-05.md §«Security & supply chain» row #45 «SLSA Level 1 / SBOM via syft» and I3 hardening Phase 3 (sigstore signing). Workflow already had id-token: write under a 'на майбутнє' comment; add attestations: write and one actions/attest-build-provenance step between Summarize SBOM and Upload SBOM artifacts. The action emits a SLSA Provenance v1.0 in-toto predicate per SBOM file (subject = sha256(file)), signed via short-lived Sigstore OIDC cert, written to GH Attestations API. Verifiable post-publish: gh attestation verify sergeant-vX.Y.Z.spdx.json --repo Skords-01/Sergeant gh attestation verify sergeant-vX.Y.Z.cdx.json --repo Skords-01/Sergeant L2/L3 ('hosted/non-falsifiable build') would require SLSA-3-generic generator workflow + reusable provenance flow — left as a separate follow-up since L1 is the project's stated bar in the PR plan. Co-Authored-By: dmytro.s.stakhov <dmytro.s.stakhov@gmail.com>
Skords-01
added a commit
that referenced
this pull request
May 6, 2026
Closes pr-plan-2026-05.md §«Security & supply chain» row #45 «SLSA Level 1 / SBOM via syft» and I3 hardening Phase 3 (sigstore signing). Workflow already had id-token: write under a 'на майбутнє' comment; add attestations: write and one actions/attest-build-provenance step between Summarize SBOM and Upload SBOM artifacts. The action emits a SLSA Provenance v1.0 in-toto predicate per SBOM file (subject = sha256(file)), signed via short-lived Sigstore OIDC cert, written to GH Attestations API. Verifiable post-publish: gh attestation verify sergeant-vX.Y.Z.spdx.json --repo Skords-01/Sergeant gh attestation verify sergeant-vX.Y.Z.cdx.json --repo Skords-01/Sergeant L2/L3 ('hosted/non-falsifiable build') would require SLSA-3-generic generator workflow + reusable provenance flow — left as a separate follow-up since L1 is the project's stated bar in the PR plan. Co-Authored-By: dmytro.s.stakhov <dmytro.s.stakhov@gmail.com>
This was referenced May 6, 2026
Skords-01
pushed a commit
that referenced
this pull request
Jun 3, 2026
…ails remain README undersold the open work (implied only Redis). Reality: all 13 stages ✅ COMPLETE/LANDED, but two tails block archival — PROPOSED #070f3 (Fizruk active-workout kv dual-write) + optional #45 Redis. https://claude.ai/code/session_01G8iiatsTtkVvwrhpsJAKWn
Skords-01
pushed a commit
that referenced
this pull request
Jun 3, 2026
Storage & Sync migration is done (all 13 stages ✅ COMPLETE/LANDED: SQLite swap, op-log dual-write, tombstones, KV swap, full-state for all 4 modules, audit-cleanup 9/9). Fast-forward archived to archive/. Resolved the last open tail before archiving: - #070f3 (Fizruk active-workout kv dual-write) — RESOLVED-as-satisfied. Investigation: the pointer is ALREADY SQLite-local via Stage 9 kv_store (safeWriteLS → webKVStore.setString → SQLite); "cross-device sync" is out-of-scope by design (kv_store is deliberately client-local, no op-log round-trip — kvStore.ts:18, migration 052:17-19). Active session is transient device-local state. Real cross-device sync would be a separate new pipeline, not a Stage-12.5 tail. - #45 Redis — opt-in optional infra follow-up, explicitly outside the roadmap's completion criteria (tracked separately). Mechanics: read-only archive frontmatter; bumped the doc's own 9 relative links +1 level; repointed 27 inbound links across 17 files (runbooks, ADRs, initiatives, audits, governance) to the archive path; moved README row active→archive; regenerated open-work (76→75) + freshness-dashboard. Gates green: docs:check-links (all resolve), check-open-work, check-today, check-freshness-*, lint:archive-move-depth. https://claude.ai/code/session_01G8iiatsTtkVvwrhpsJAKWn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ше >60%)
Made-with: Cursor