chore(straymark): upgrade framework fw-4.19.0 → fw-4.20.0#44
Merged
Conversation
Vendored StrayMark framework bump applied via `straymark update-framework`.
Crystallizes POLISH-CHARTER-PATTERN v0→v1 (N=2) thanks to two findings this
repo filed upstream in StrangeDaysTech/straymark:
- #209: sub-class 5 (shipped-mitigation regression via un-updated
downstream consumer) + `analyze declared-vs-wired` subcommand.
- #210: `charter new` reconnaissance discipline + CHARTER-FILES-EXIST rule.
Also adds .straymark/QUICK-REFERENCE.md one-pager, charter-template +
charter-new SKILL guidance, config.yml complexity/china comments, and the
fw-4.20.0 footer bump across governance docs + i18n (es, zh-CN). Records
AILOG-2026-06-01-001 documenting the upgrade.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resumen
Versiona la actualización del framework StrayMark vendored
fw-4.19.0→fw-4.20.0,ya aplicada en el working tree con
straymark update-framework(CLIcli-3.18.0).straymark statusconfirma Frameworkfw-4.20.0y estructura 17/17 OK.Lo relevante: POLISH-CHARTER-PATTERN graduado v0 → v1 (N=2)
Esta versión crystalliza el
POLISH-CHARTER-PATTERNde v0 (N=1) a v1 (N=2), yLNXDrive es el segundo dominio independiente que valida el patrón (daemon Rust de
cloud-sync + escritorio GTK, frente al backend Go de Sentinel que lo originó).
La graduación provino de dos findings que este repo publicó upstream en
StrangeDaysTech/straymark:("shipped-mitigation regression vía un consumidor downstream no actualizado": el caso
daemon D-Bus ↔ cliente GTK con
#[cfg(feature = "goa")]nunca definido) y cruza el gateN=2 para el subcomando
straymark analyze declared-vs-wired.charter new("READ antes de declarar") y la regla de validación
CHARTER-FILES-EXIST.Cambios incluidos
POLISH-CHARTER-PATTERN.md(v0→v1, sub-clase 5, créditos #209/#210);charter-template.md(+ i18n es, zh-CN) con guía de reconocimiento y de listar todos losconsumidores cross-component;
straymark-charter-new/SKILL.md(.claude/.codex/.gemini)con el recordatorio de reconocimiento;
config.yml(comentarioscomplexity.thresholdyscope
china); nuevo.straymark/QUICK-REFERENCE.md(one-pager).dist-manifest.yml4.19.0→4.20.0; bump de footerfw-4.20.0en docs degovernance + i18n;
.checksums.jsonregenerado; limpieza de whitespace tras<!-- straymark:end -->; cambios de modo100755→100644.AILOG-2026-06-01-001documenta el bump y su origen.Verificación
straymark status→ Frameworkfw-4.20.0, estructura 17/17 OK.straymark validate→ 0 errores, 8 warnings SEC-001 pre-existentes (token/Bearer enAILOGs antiguos, no introducidos aquí).
🤖 Generated with Claude Code