sans les flex - #2
Merged
ThomasWatanabeVermorel merged 1 commit intoMar 25, 2020
Merged
Conversation
jsboige
pushed a commit
that referenced
this pull request
Jun 30, 2025
sans les flex Former-commit-id: afe7607 Former-commit-id: 7daa4efaecddbc830b01491e867e7c446f055af4
jsboige
added a commit
that referenced
this pull request
Feb 20, 2026
Issue #2 (Rules CSS styling) deferred pending design decision. Documented 3 solution options: - A: Add game_type column to CSV - B: Create separate templates per variant - C: CSS based on markdown h2 content (recommended) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jsboige
added a commit
that referenced
this pull request
Feb 20, 2026
Add distinct color themes for the 4 new game variants in Rules: - Bingo (cards 7-10): Orange theme (#ff6600) - Dernier beau parleur (cards 11-15): Blue theme (#0066cc) - Moulin à baratin (cards 16-20): Green theme (#228b22) - Parlote coinchée (cards 21-24): Purple theme (#7b2d9e) Resolves Issue #2 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
4 tasks
4 tasks
3 tasks
3 tasks
This was referenced Jun 15, 2026
jsboige
added a commit
that referenced
this pull request
Jun 18, 2026
…5→≥21 (jsboige decision #2) (#531) jsboige interactive decision #2 (issue #458, 2026-06-18): "Je suis pour l'upgrade complète, même si c'est plus lourde" → target = 10.3.2-latest + 2sxc 15→≥21 + template audit. Supersedes the 10.1.2 target of #520/#522/ #527/#528. #445 Stripe Native unblocked (OpenStore blocker dissolved). Net-new decision-spec (131-target-revision-10.3.2-full-upgrade.md, +141): - The 6-phase go-live procedure (#527) + rollback contract + .NET 4.8 runtime finding remain valid; only target + 2sxc scope change. - 2sxc upgrade path: 15.02 → 21.07 LTS on DNN 9.11.1 (2sxc-first), then DNN → 10.3.2. Adds new Phase 1.5 + expanded Phase 3/4 (content migration is now real, unlike the 10.1.2 no-op). - KEY GROUNDED FINDING (§3): the template audit is largely ALREADY DONE. All 4 Argumentum custom templates already use @inherits Custom.Hybrid.Razor14 (verified, not asserted) — the legacy RazorComponent migration #131 flagged is complete. APIs in use (App.Query, AsList, CmsContext, Link.To, Edit.TagToolbar) all maintained in 2sxc 21. Residual risk is the 25 stock apps' v20 infra changes (staging-test item, not repo-audit). Superseded banners added to the 4 target-bearing runbooks pointing to the new decision-spec as source of truth (#520, #522, #527 §4 "no 2sxc migration" explicitly invalidated, #511 errata redirected). No merged history rewritten. Doc-only, non-gated. Execution (deploy/upgrade/2sxc) stays GATED jsboige. No prod mutation, no DB/RDP, no template edit. Refs #131 #458 #445 #514 #520 #522 #527 #528. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Jun 18, 2026
Merged
jsboige
added a commit
that referenced
this pull request
Jun 19, 2026
…rget, recommend closure (#547) Closure assessment for #498 (dispatched by ai-01, PRIMARY). Evaluates cluster-level coverage against the #498 target and recommends CLOSURE of #498 (content-proposal layer), with phase-4 mopup documented as optional finish. Key findings (all verified against the real 1408-row prod Fallacies CSV, master 4dd3c6b): - 70 direct cluster AIF mappings (depth 2-4), broadMatch-dominant (57/10/3) — intact, no regression from phases 1-3. - Effective coverage by inheritance: 1292/1408 = 91.8% (direct+inherited). - The "~31% (442/1408)" figure in the issue body is jsboige's measure with unspecified derivation — recorded transparently rather than reproduced (DoD #5 fail-loud on the metric). - Generative work (phases 1-3): 50 depth-3 leaves with full triple-AIF exception structures, 17 distinct Walton schemes, 49 distinct CA-nodes. rebut-type progression (absent phases 1-2, appears phase 3) is independent semantic-fidelity evidence. - Phase-4 mopup (13 remaining depth-3 leaves) is OPTIONAL, not a gap: all 13 already carry native cluster AIF skos mappings in prod. Phase 4 would add generative density (50->63/63), not coverage. - Fail-loud: the 4 unmapped depth-2 categorical parents (Technique rhetorique, Appel a l'emotion, Conclusion mathematique invalide, Sabotage du debat) are category umbrellas whose children carry the mapping — no scheme fabricated. DoD assessment: #1 (numbering) met, #2 (generative structures) met for 50 leaves, #3 (mapping-type coherence) met, #4 (fail-loud) met. No coverage gap. Recommends closure; gated prod write + OWL regen + jsboige content validation remain as separate downstream gates. Doc-only gated. No production data changed. Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
jsboige
added a commit
that referenced
this pull request
Jun 19, 2026
…x new arc docs (#550) Refresh the v0.9.0 release dossier so it is presentation-ready for jsboige. Targeted staleness fix, not a rewrite (+16/-4). - Header: refreshed date/base (master 4dd3c6b) + refresh-note block documenting the 3 corrections - §2 doc-map: index the 3 new DNN upgrade-arc docs that merged since #526 (#531 target revision 10.3.2, #543 2sxc migration plan Phase 1.5, #548 DNN Phase 2 exec+rollback) — relevant to the "coupled DNN" release - §4 gate checklist: the DNN #131 point said "10.1.2 vs 10.3.2 undecided" — that is now confirmed 10.3.2 + 2sxc 21 (decision #2, #531); updated to reflect the decision + point to the procedure docs - Artifact inventory re-verified against disk: 64 PDFs (8 langs × 8 types) still present, mindmaps es/ar/fa/zh still 0 (foreground-lock) No structural change. No tag, no release, no regen, no README/CHANGELOG edit. Gated jsboige for the actual release. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Jun 27, 2026
jsboige
added a commit
that referenced
this pull request
Jul 1, 2026
… (0 errors, 0 Cards/) (#618) PRIMAIRE of ai-01 deep-queue #2 (dispatch msg-...92kynx). Produces the candidate-URL output behind the #600 §5.1 probe ceiling. Ran tools/link-langlinks-resolve.py (PR #610, merged) over full Fallacies + Virtues taxonomy: 829 articles probed -> 2934 candidate link_<lang> URLs (fallacies 2754, virtues 180), 0 errors. Materializes the ~57% probe ceiling (~2919 cells) into concrete reviewable URLs. Step 1 of #600 §6 methodology. Per-lang: ru 371, pt 430, es 513, ar 603, fa 480, zh 537. Resolves FROM link_en (Wikipedia only); 433 non-Wikipedia curated sources excluded + preserved (#600 §6.2). Quality verified: - URL encoding correct per script (Cyrillic %D0, Arabic %D8, Persian %D8, CJK %E8, PT/ES Latin unencoded). - Homonym scan (#600 §6.4) of 1620 AR/FA/ZH candidates: 0 real leaks. AR 0/603, FA 0/480 Latin-path; ZH 3/537 (0.6%) = legit loanwords/ acronyms (FUD x2, Creepypasta) — not errors. The "Engagement" homonym from PR #610 sample does NOT recur at scale (isolated case). - Asymmetry: virtues ru/pt = 4 each (sparse abstract-concept coverage) vs ar/fa/zh 46-56 — coverage reality, flagged for spot-validation. Sidecars (reviewable snapshot, UTF-8 no-BOM LF): - docs/taxonomy/600-link-resolve-fallacies.csv (2754 rows) - docs/taxonomy/600-link-resolve-virtues.csv (180 rows) schema: dataset,key,link_lang,resolved_url Robustness: try/except + continue (skip on network error, never abort) -> 0 errors/829. Public MediaWiki API, no key, 0.3s throttle, descriptive UA. Next (gated post-release): apply PR consumes sidecar -> cell-by-cell drift-free (QUOTE_MINIMAL+CRLF, method #595), skip non-empty, human spot-validate ~5% AR/FA/ZH residue (~150 cells), re-run probe to confirm gap closed. Scope: docs/taxonomy/ only. 0 write Cards/, 0 AssetConverter code change (pre-tag safe). Base 18b4d02. Relates to #600, #606, #610. Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude-Code <noreply@anthropic.com>
This was referenced Jul 3, 2026
jsboige
added a commit
that referenced
this pull request
Jul 3, 2026
…shed pack (#663) Tertiaire dispatch kp26j6. Refines the #415 Phase-2 proposal (PR #628, read-only, no execution). Re-measured on current master 9c19e51 (was 33b1c0b at proposal time). Two findings that sharpen the plan: 1. Mindmapper gap (186.7 MB) — the proposed git filter-repo --path prefixes are exact-prefix matches and MISS two sibling build-output trees: - .../AssetConverter/Mindmapper/Published/ (129.2 MB) - Cartes/Generation/Mindmap/Mindmapper/Published/ (57.5 MB) These are regenerable dotnet-publish output (.csproj/.sln committed in history, binaries deleted at HEAD, .REMOVED.git-id sentinels alongside). Corrected strip target = ~1.8 GB (proposal said ~1.557 GB). The --path set is updated to close the gap; they were misclassified into the "other" zone by the audit path regex. 2. Pack grew 2.05 -> 2.08 GiB (+3868 objects) but the growth is text/code only (other zone 882.8 -> 946.7 MB); regenerable binary zones byte-for-byte unchanged. Bloat source is NOT recurring — no new build artifacts committed. Risk #2 currency update: open PRs 8 -> 3 (#596/#661/#662), lowering rewrite risk. READ-ONLY per DoD: 0 history mutation, 0 force-push, 0 clone, 0 Cards/ write. Reproducible via python tools/git-weight-audit.py + scratchpad 415_mindmapper_gap.py. Go/no-go = jsboige. Recommendation (DEFER post-tag) unchanged. Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude-Code <noreply@anthropic.com>
jsboige
added a commit
that referenced
this pull request
Jul 4, 2026
…-only binary scan) (#687) Dispatch lev5ct primary (2sxc export unblocked, voie #2 = local backup scan). Read-only extraction from the production DNN backup to unblock the i18n portage field-model decision (#682). Findings (signal, not PASS): - Rule content-type uses GENERIC single-value fields (EntityTitle, Summary, Material, MinNbPlayers, ...) — confirmed at DB level. ZERO language-suffixed fields (Summary_en/Summary_fr absent). Confirms #669 §2c from the view audit. - Production EAV is dimensioned FR+EN only. ru/ar/fa/zh = trace noise; pt/es absent. The 6 release target languages are NOT usable EAV dimensions today. - => #682 field-model decision effectively FORCED toward Path A (lang-suffixed + loc(), mirror #490 / PR #674): Path B (EAV dimensions) would require enabling 5 new DNN content cultures before any translation can attach. Blocker (honest): clean SQL restore denied — jsboi Windows login is not sysadmin on MSSQL$SQLEXPRESS, sa password not in keychain (not guessed, out of read-only scope). Two clean unblockers documented (sysadmin grant OR sa pwd OR voie-1 Playwright export). The binary-scan findings are already conclusive for the portage-direction decision; full per-attribute enumeration gated on the unblocker. Gate: read-only. No prod write, no DB mutation, no credential in the diff. Refs #681, #682, #674, #669. Dispatch msg-20260704T130644-lev5ct. Co-authored-by: Claude-Code <noreply@anthropic.com>
jsboige
added a commit
that referenced
this pull request
Jul 8, 2026
…ll prep, gated execution (#754) Consolidated tools/499-virtues-aif-columns-apply.py — the MIRROR of the Fallacies contract (PR #753, #498/#707§4a). Applies the ratified deterministic back-fill (plan #750 v2) to Cards/Fallacies/Argumentum Virtues - Taxonomy.csv, adding the same 2 columns (AIF_attackType + AIF_attackedNode) so both taxonomies share an identical AIF column contract (anti-drift). Derivation (plan #750 v2, re-confirmed programmatically on master): default undercut/RA-node override undermine/I-node if opposes {889, 804} (fabricated premise) override rebut/CA-node if opposes {340} (counter-conclusion) Distribution EXACT: 206 undercut + 13 undermine + 3 rebut = 222 nodes with scheme; 1 root node (pk 0, no scheme) = empty. Technique: byte-exact surgical (same as Fallacies script, memory [[csv-byte-exact-column-insertion]]). Re-writes NO existing field. Verified dry-run: 0 byte-preservation mismatch; placement after AIF_skosMappingType (idx 77), print_and_play shifts to 80. ⚠ GATED EXECUTION: dry-run by default. Apply ONLY after the Fallacies contract (PR #753) is merged + reviewed (ai-01 + jsboige veto). 0 write to Virtues prod CSV in this PR — script only. Placement constant (INSERT_AFTER_IDX=77) stays anti-drift with whatever the Fallacies PR #753 open-question-#2 decision lands. This is [secondaire] prep work — reduces post-unblock cycle time: once the contract merges, the mirror is 1 PR (run --write). No blocker removed, no gate crossed. Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude-Code <noreply@anthropic.com>
jsboige
added a commit
that referenced
this pull request
Jul 16, 2026
…ppers (read-only, 0 write) (#821) Read-only check on the 29 integrated HTML mindmap wrappers regenerated by #819 (the T&A review vehicle for gate (b)), extending the #818 encoding thread. Answers a concrete de-risking question: did the #804 residual #3 (.content.svg declare encoding="utf-16" but are UTF-8+BOM, ai-01 Cycle H) propagate into the file Thomas & Adeline actually open? Result: NO. 0/29 wrappers carry the latent. - 29/29 are really UTF-8, declare charset=UTF-8 (meta). - 0 utf-16-declared-but-utf8 mismatches. - Cause: MindMapHtmlWrapper.FormatWrapper strips the <?xml?> prologue and injects the SVG into an HTML shell with its own charset=UTF-8, so the erroneous utf-16 declaration is eliminated, not inherited. Independently corroborates ai-01's Cycle H localization certification (SHA256 #636 + script composition) on the freshest artifact (#819). Tracked-not-fixed observation: 4/29 wrappers carry a BOM (Fallacies_{ar,es,fa,zh}.html) — harmless (meta charset + BOM precedence) but inconsistent. Fix = po-2023 regen lane (mindmaps), not po-2024 (Cards). Folded into po-2023's post-tag mindmap regen pass (#804 #1/#2/#3). Out of scope: wrapper/.content.svg regen, MindMapHtmlWrapper edit, BOM strip — all lane po-2023. No write prod this PR. Refs: #819, #804 residu #3, #818, #458. Co-authored-by: Your <your.email@example.com> 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.
No description provided.