Skip to content

IPADP Phase 3: L3 Upstream Sync Automation #15

Description

@satwareAG-ironMike

IPADP Phase 3 — L3 Upstream Sync Automation

Track the remaining L3 conformance work for this fork (IPADP project #6). The L3 row in AGENTS.md commits us to automated upstream sync + morning protocol integration. The scripts already exist; this milestone wires them into CI and the Cline daily workflow.

Context

Goal

Reach L3 conformance by automating upstream-release detection and integrating the Cline Start-of-Day / End-of-Day protocols into the repository's daily routine.

Proposed sub-issues

  1. CI: Scheduled upstream-sync check

    • New GitHub Actions workflow (e.g. .github/workflows/upstream-sync-check.yml) on a daily cron.
    • Wraps scripts/bash/check-upstream-sync.sh.
    • When a new upstream tag is detected, auto-opens an issue (labelled upstream-sync) with release notes link and suggested merge branch name (sync/upstream-<tag>).
    • Idempotent: does not open duplicates for the same tag.
  2. Repo-local SoD/EoD protocol hooks

    • Add scripts/bash/sod.sh and scripts/bash/eod.sh thin wrappers that source ~/Documents/Cline/Workflows/sod.protocol.md / eod.protocol.md when present, and fall back to a documented local default otherwise.
    • Integrate into scripts/daily-routine.sh (referenced in the Morning Start Protocol).
    • Invoke check-upstream-sync.sh and check-privacy-leaks.sh as part of SoD.
  3. Documentation

    • Update AGENTS.md L3 row to reference the new workflow + scripts.
    • Update specs/metadata.json (conformance.level evidence pointers).
    • Add a short docs/ipadp-l3-automation.md describing the flow.

Acceptance criteria (milestone-level)

  • Scheduled workflow runs daily and opens an issue on a new upstream tag.
  • scripts/daily-routine.sh sod and ... eod exist and succeed on a clean checkout.
  • check-privacy-leaks.sh and check-upstream-sync.sh both run green on main-speck.
  • AGENTS.md + specs/metadata.json updated to reflect L3 conformance.
  • All 835+ integration tests still green (uv run pytest tests/integrations/ -x -q).

References

/cc @jane-alesi

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions