Skip to content

chore: back-merge release/v0.1.8 into develop#43

Merged
explosivebit merged 2 commits into
developfrom
chore/back-merge-v0.1.8
May 6, 2026
Merged

chore: back-merge release/v0.1.8 into develop#43
explosivebit merged 2 commits into
developfrom
chore/back-merge-v0.1.8

Conversation

@explosivebit
Copy link
Copy Markdown
Contributor

Summary

Back-merge of release/v0.1.8 (now merged into main, tagged v0.1.8, published to npm with provenance) into develop so the version bump and any release-only commits don't get lost.

Per guides/GIT-FLOW-GUIDE.ru.md §6.10.

What's in this back-merge

No new code changes — release was already QA'd through PR #42 (3-OS smoke matrix green, npm publish workflow success).

🤖 Generated with Claude Code

F11 (body preview + decision impact drill-down — PRD-006/RFC-005),
F12 (stale + blind-spot push notifications — PRD-007/RFC-006),
F13 (Copy as markdown — tactical), and F14 (post-audit cleanup —
7 HIGH + 7 MEDIUM/LOW from 5-expert audit). Plus the
HomePage health-poll effect-cycle hotfix.

All artifacts (PRD-006/007 + RFC-005/006) active with R_eff > 0
via EVID-014 / EVID-015.

Refs: PRD-006 RFC-005 PRD-007 RFC-006
@explosivebit explosivebit merged commit f667af7 into develop May 6, 2026
3 checks passed
@explosivebit explosivebit deleted the chore/back-merge-v0.1.8 branch May 6, 2026 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant