Repository navigation
Conversation
# Conflicts: # archify.zip
Agents may now snooze or ignore a reminder when the user explicitly asks, and the notice tells users that option exists. The child derives its fetch timeout from the remaining deadline so a slow network records a failed check and backs off instead of being killed on each delivery; finalize gives the check the time its gates already take. Tests keep update state out of the user cache. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
The delivery reminder is now the only update-check behavior. Remove the acknowledgement mode, its offered/acknowledged digest history, legacy cache migration, and the separate 72-hour schedule. Cached candidates always carry their check time, failed checks keep repeating the last validated release, and snooze/ignore stay the only suppressions. Concurrency tests that used acknowledgement as the second writer now use snooze, so cache-safety coverage is kept. README check intervals now say 24 hours. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Keep update notices in diagram delivery receipts
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: tt-a1i/archify/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (19)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 SummaryUpdate checks now run during WalkthroughThe update checker now checks successful manifests about every 24 hours and stores snooze or ignore preferences by release. Standalone delivery and finalize run bounded update checks and include results in success and failure receipts. Text output includes a notice when required. Documentation and tests reflect the updated checker behavior and delivery flow. Priority: ➖ Normal Estimated code review effort: 4 (Complex) | ~45 minutes Merge Risk: ⚪ Minimal · up to No identified issue blocks this update-reminder change from merging after normal checks. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The new reminders use a bounded check against a fixed update source, and no security bypass was established. The remaining uncertainty is how the exported checker could be used by integrations outside the shown delivery paths. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
Resilience and Maintainability Implications
Hardening Proposals
🚥 Pre-merge checks | ❌ 2❌ Failed checks (2 warnings)
Full details: Contribution ScopeExplanation The implementation stays focused on update reminders, but the PR does not provide all required scope facts for this broad contract change. The diff changes cache state from schema 1 to schema 2 and removes legacy cache migration, adds new 1-second/4-second deadlines, and changes receipt and Resolution Update the PR description with an explicit linked issue or recorded maintainer scope decision. Document the schema-v1 cache handling, receipt compatibility, Full details: Validation EvidenceExplanation Concrete validation gaps remain. The changed source has strong automated coverage: the new tests cover repeated reminders, deadlines, slow networks, cache-claim recovery, deliver/finalize receipts, failure paths, disabled checks, and artifact identity. The author-reported CI run for c888c86 passed the Node matrix, browser/WebM, package smoke, Windows, ZIP freshness, manifest, and website gates. The reviewed head 922c1ca has the same tree as c888c86, so that result is reusable for the code and generated archive. However, CONTRIBUTING.md requires maintainers to use a promoted revision on real diagram tasks and record the tested revision, usage evidence, and unresolved issues. The PR reports only an earlier isolated package with a mock cache, says the final-package trial is in progress, and says a second client is unverified. The PR also says it adds no generated changes, while the authoritative diff changes archify.zip; the body should describe that generated artifact accurately. Resolution Before promotion, have maintainers run representative real diagram tasks against the exact head 922c1ca (or its exact package), then record the revision, client/host, task outcomes, stability result, and unresolved issues. Correct the generated-artifacts section to list archify.zip as changed in the reviewed range, explain that it was rebuilt in Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Thanks @tt-a1i for contributing to Archify! Your work is now part of the project.
|
1 participant
Problem and value
Promote the update-reminder behavior integrated by #599 at
dev@922c1cadto stablemain. An older Skill could previously discover a new Release and then silently suppress the reminder before the user's final reply. Finalize and standalone deliver now include one bounded, repeated notice until the user updates or explicitly chooses snooze/ignore.Stability impact
The PR changes the Skill, delivery receipts and update checker; it does not change the 3.0.0 release identity or public stable manifest. The fixed manifest origin and validation, canonical diagram bytes, quality exits and path defenses remain intact. The full design and behavior contract are in #599. One Codex client ran two ordinary diagram tasks against an isolated earlier package and mock valid update cache; the user's local 3.0.0 trial of the final package is in progress. A second client remains unverified.
Tests run
c888c860: CI run 36436196454 passed Node 18/20/22/24 suites, Windows path checks, WebM/browser, three-platform package smoke, ZIP freshness, published-manifest and website gates.Generated artifacts
archify.zipchanges in this PR: it was rebuilt in #599 from the final source with official Node 22, and exact-head ZIP freshness plus three-platform package smoke passed. Gallery and Viewer sources are unchanged by the reminder behavior.