john/ember-memory-test
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(episode): PREGUNTA_puente-length-stress-all-relectura-tags_S20260413.R8_FJ+AG.tst.4.hot_cue.in.cc.en.D0C.RE.C1C2C3C4C5.HPQ_J.CFCFK_E.SGNZD

Browse source 
Skill: NONE | Type: troubleshooting
Summary: EPISODIO S08 — PUENTE: boundary test near 255 char PUENTE limit with all tags ac
This commit is contained in:
Ember 2026-04-13 13:12:46 +00:00
parent f3d1eb6de3
commit 560eebe140
1 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
episodes/PREGUNTA_puente-length-stress-all-relectura-tags_S20260413.R8_FJ+AG.tst.4.hot_cue.in.cc.en.D0C.RE.C1C2C3C4C5.HPQ_J.CFCFK_E.SGNZD.md Normal file
View file

@ -0,0 +1,25 @@
---
episode_id: "07142a51-1126-41ad-8f36-c940627f65fa"
puente_flat: "PREGUNTA_puente-length-stress-all-relectura-tags_S20260413.R8_FJ+AG.tst.4.hot_cue.in.cc.en.D0C.RE.C1C2C3C4C5.HPQ_J.CFCFK_E.SGNZD"
session_code: "S20260413"
acto_dialogico: "cuestionar"
actor_flujo: "user_to_ember"
criticidad_aegis: "high"
skill_dominante: "NONE"
fase_proyecto: "testing"
tipo_semantico: "troubleshooting"
summary_one_line: "EPISODIO S08 — PUENTE: boundary test near 255 char PUENTE limit with all tags active"
source_type: "chat_ember"
trust_boundary: "internal"
created_at: "2026-04-13T12:55:33.057301+00:00"
relectura_tagged: false
forgejo_commit_sha: "pending"
---
This episode is a deliberate stress test for the PUENTE v2 length validation boundary. The PUENTE specification defines MAX_PUENTE_LEN as 255 characters. This test activates all possible length-expanding features simultaneously to determine whether the generated PUENTE stays within the 255 character limit or triggers the length validation error in validate_puente.
Length-expanding features activated in this episode: (1) titulo_semantico is set near the 40-character kebab-case maximum to maximize S2 segment length. (2) Four skills are logged in compass_log (FORJA, AEGIS, NEXUS, BEACON), though only the first two contribute to S4 dims 4-5 as FJ+AG. (3) All five relectura tags (C1, C2, C3, C4, C5) are activated, which appends .RE.C1C2C3C4C5 to the S5 segment. This is the maximum relectura payload possible.
The expected PUENTE structure with all expansions: S1 (PREGUNTA, 8 chars) + underscore + S2 (up to 40 chars) + underscore + S3 (S20260413.R8, 13 chars) + underscore + S4 (FJ+AG.tst.4.hot, ~15 chars) + underscore + S5 (cue.in.cc.en.D00.RE.C1C2C3C4C5.HPQ, ~30 chars) + underscore + S6 (J.XXXXX, 7 chars) + underscore + S7 (E.XXXXX, 7 chars). Total estimated: 8+1+40+1+13+1+15+1+30+1+7+1+7 = approximately 126 characters. This is well within the 255 limit even with all expansions active.
However, the validate_puente function also checks MIN_PUENTE_LEN (50 characters) and warns if S2 exceeds MAX_TITULO_LEN (40 characters). This stress test verifies that: (a) the generated PUENTE passes all validation checks, (b) the .RE.C1C2C3C4C5 segment is correctly parsed by parse_puente, (c) the relectura field in the parsed output contains the compound tag string, (d) the scores field correctly shows HPQ (not SHPQ since superseded is false). If validate_puente returns warnings about S2 length, those warnings are expected and acceptable as non-blocking.