Stand: 2026-04-01

J01-95 72-15 Journalisierten Jira-/Pages-Sync mit Resume aufbauen
Type
Subtask
Status
Erledigt
Priority
Medium
Assignee
-
Sprint
-
Sprint role
-
Resolution
Fertig
Updated
2026-04-01T12:52:36.637+0200
Parent
J01-72
Related issues
Relates to: J01-119 — Gezielten Jira-/Pages-Sync gegen stille Rückschritte härten — Erledigt

Contents key

This page

Canonical public work status for J01-95. This step adds a local journal and resume path to the Jira/pages workflow for known Jira and GitHub Pages changes.

Goal

Replay known Jira or GitHub Pages changes in a targeted way, without relying on project-wide Jira list queries in the normal mode.

Implemented now

  • new project-specific skill jira-state-sync/ for journaled and resumed runs
  • canonical normal path via skills/jira-state-sync/scripts/run-sync.sh
  • local Jira working state under .local/jira-sync-cache/
  • local run journal under .local/jira-sync-journal/
  • a guard before writing _data/jira_pages/issues.json
    • targeted runs stop when untouched issues would regress
    • those cases are recorded as failures in the run journal
    • a deliberate full refresh is required afterwards
  • the public Jira generator still accepts local input files for the existing V1 workflow
  • verify-public-jira-pages.sh can now verify only affected keys
  • new Pages helpers to:
    • derive link changes from Git diffs
    • find affected Jira keys locally from public Jira files
  • atlassian jira ext remotelink sync for targeted docs link synchronization
  • The issue is now set to Done in Jira; targeted status and remote-link runs for J01-95 were pulled through successfully.

V1 Rules

  • Jira changes are recorded as KEY:CLASS.
  • V1 classes: status, summary, description, step_meta, remote_links
  • targeted runs only write when the guard finds no regressions on untouched issues
  • GitHub Pages changes are detected from a Git base ref.
  • In V1, jira/ is treated as the complete public view of docs-domain links imported from Jira; other Jira content stays outside this path.
  • Full sync remains a repair mode, not the default path.
  • Follow-up work after the completed V1 base now continues in J01-119.

Completion

  • V1 delivers a journaled normal mode for known Jira and GitHub Pages changes.
  • Resume, targeted verification, guard-based aborts, and the full-refresh repair path are now part of the workflow.
  • Any further hardening now lives in follow-up work, not under J01-95.