vibesubin 0.6.0

vibesubin 0.6.0

Two opt-in output styles, a canonical conflict surface, a two-track ship-cycle, and a 5-category README — plus the usual tightening.

Layperson mode (opt-in)

Triggers: /vibesubin explain, /vibesubin easy, "쉽게 설명해줘", "일반인도 이해되게", "explain like I'm non-technical", "initiate easy mode", "非開発者でも分かるように", "用通俗的话解释".

Every finding now gets three plain-language questions answered — 왜 이것을 해야 하나요? / 왜 중요한 작업인가요? / 그래서 무엇을 하나요? — in a pretty box format, with severity translated to urgency (CRITICAL → "지금 당장", HIGH → "이번 주 안에", MEDIUM → "다음 릴리즈 전까지", LOW → "시간 날 때"). Stacks freely with tone=harsh. Same findings, same evidence, same file:line references — presentation-only. Full rules in plugins/vibesubin/skills/vibesubin/references/layperson-translation.md.

Skill conflicts surface — gap / reason / basis

When two specialists give contradictory advice on the same file, the umbrella now emits a ⚠ Skill conflict block with both sides' recommendation + reason + evidence basis — and the operator picks. Four canonical pairs seeded in plugins/vibesubin/skills/vibesubin/references/skill-conflicts.md:

• refactor-verify ↔ audit-security on sequencing (ACTIVE vs. LATENT vulnerability)
• unify-design ↔ refactor-verify on component consolidation (hand-off, not conflict)
• fight-repo-rot ↔ project-conventions on dead dependencies (remove-then-verify-lockfile)
• manage-secrets-env ↔ audit-security on tracked .env (required sequence: rotate first, then structural fix)

Contradiction is information, not a bug — the catalog decides between hand-off (sequence) vs. true conflict (fork) and surfaces evidence either way.

ship-cycle — enforced conventions + two tracks

PR / branch / commit conventions are now enforced via a new reference file (plugins/vibesubin/skills/ship-cycle/references/pr-branch-conventions.md):

• GitHub Flow branches: <type>/<issue-N>-<slug> (e.g., fix/issue-42-auth-session-refresh)
• Conventional Commits + mandatory Closes #<N> footer
• Six-section PR template: Context / What changed / Test plan / Docs plan / Risk / Handoff notes
• Rebase-first merge with --force-with-lease (plain --force banned)
• No force-push to main / master / release/*
• CI green gate: all checks (including optional) must be SUCCESS or NEUTRAL; SKIPPED requires confirmation; flaky checks get one re-run
• Merge strategy detection: repo settings first, CONTRIBUTING.md second, --squash default

Two tracks. The default GitHub track is unchanged. The new PRD track handles every other host (GitLab, Gitea, Forgejo, Bitbucket, plain git, gh unauthenticated) — local markdown files under docs/release-cycle/vX.Y.Z/ carry the same methodology, same conventions, same audit trail. ship-cycle no longer hard-exits on non-GitHub hosts.

See plugins/vibesubin/skills/ship-cycle/references/prd-track.md.

READMEs — 5 categories across 4 languages

Single lineup table split into 5 category-grouped tables:

• Code quality (5): refactor-verify, audit-security, fight-repo-rot, manage-assets, unify-design
• Docs & AI-friendliness (2): write-for-ai, project-conventions
• Infra & config (2): setup-ci, manage-secrets-env
• Release process (1): ship-cycle
• Host-specific wrappers (1): codex-fix

Per-skill writeups tightened under the same 5 headings; anchors plain (#refactor-verify, no #1-refactor-verify numbering). Structure mirrors in README.ko.md, README.ja.md, README.zh.md with each file's voice preserved. Total across 4 languages: 1248 → 1190 lines.

Under the hood

• Every 11 worker SKILL.md file gained a ## Layperson mode — plain-language translation section, parallel to the existing ## Harsh mode — no hedging.
• Umbrella synthesis Step 3 gained two rules — skill-conflict check + layperson-layer application.
• ship-cycle gained ### Step 1.5 — Track selection between Step 1 and Step 2.
• Assumptions block gained Track: and Merge strategy: fields.
• .gitignore explicitly lists .mypy_cache/ and .pytest_cache/. Caches must never be tracked.

Full detail: CHANGELOG.md.