Work page with project entriesСтраница работ с карточками проектов

StatusСтатус
completeзавершён
ServiceСервис
portfolio
IssueIssue
#7
Pull requestPull request
#28
ReleaseРелиз
0.1.4
Lead time (h)Время цикла (ч)
8.0

What this cycle decidedЧто решил этот цикл

The site now has /work/: fourteen projects in two ordered groups (Platform, Products), each rendered as a card with a bilingual one-line summary, stack chips read from frontmatter, and a native <details> block that expands into the rendered markdown body, links and a metrics placeholder — zero JavaScript, no third-party request.На сайте появилась страница /work/: четырнадцать проектов в двух упорядоченных группах (Платформа, Продукты), каждая карточка — двуязычное краткое описание, чипы стека из frontmatter и нативный блок <details>, разворачивающий отрендеренное markdown-тело, ссылки и заглушку метрик — без JavaScript и сторонних запросов.

TimelineХронология

  1. Issue openedIssue открыт:
  2. Proposal approvedПредложение одобрено: +6 h 32 min+6 ч 32 мин
  3. MergedСмержено: +1 h 20 min+1 ч 20 мин
  4. ReleasedРелиз выпущен: +5 min+5 мин

Manual interventionsРучные вмешательства

Each record below is quoted verbatim in English, the language it was written in.

Каждая запись ниже приводится дословно по-английски — на языке, на котором она была написана.

  1. amended issue #7 with an explicit requirement to inline every string, then re-ran the investigator

    the first proposal pointed at the issue's wording instead of embedding it, and the implementer — which never sees the issue — correctly refused to invent fourteen projects' bilingual prose

    2026-09-11T04:35:34Z

  2. deleted the failed proposal directory through a reviewed GitOps pull request

    the investigator only overwrites a proposal at status proposed, and the failed one sat at needs-triage, so the loop had no way back in

    2026-09-11T04:58:45Z

  3. rewrote pull request #28's description by hand with the link-check output, the same-origin evidence and the keyboard evidence

    three acceptance criteria demanded that evidence in the pull request body, which the implementer opens from a fixed template and cannot edit

    2026-09-11T05:37:09Z

  4. rewrote the equivalent criteria in issues #8, #10 and #11 so the artifact is a committed file or a script in npm test

    the same defect was waiting in three later cycles; naming human-only verification as a reviewer step instead of a criterion prevents three more deadlocks

    2026-09-11T05:37:35Z

  5. added two rules to AGENTS.md: an acceptance criterion must be satisfiable by a commit, and the copy is the contract

    fixing the three issues by hand leaves the next author free to write the same unsatisfiable criterion again

    2026-09-11T05:45:53Z

  6. ran the shepherd by hand for this slug

    the cron shepherd skips a slug it believes a live DevLoopWorkflow is driving, and a workflow left Running from an earlier attempt held that claim without doing any work

    2026-09-11T06:23:06Z

  7. merged pull request #28 by hand

    the review was approved with no blocking findings and every check was green, but GitHub had re-anchored an already-fixed comment onto the new head, so the shepherd read it as current, exhausted its attempts and parked the proposal at review-stuck

    2026-09-11T06:41:07Z

Back to the colophonНазад к колофону