ac276e9d4b
docs(ms-ai-architect): KB-refresh tema-a steg 1 — modellkatalog GPT-5.1→5.5 i 2 critical cost-filer
...
Reconcile stale lokale modell-enumereringer mot kanonisk model-catalog-2026.md
(2026-06-18, live-verifisert). Pilot: 4 critical cost-filer auditert (~400k tokens),
2 hadde reell content-drift (modellkatalog en generasjon bak), 2 kun naming/noise.
- model-selection-price-performance.md: GA-modell-snapshot utvidet fra GPT-5/4.1 til
hele GPT-5.1→5.5-generasjonen + o-serien + pointer til catalog. Tiering-anbefalinger
flagget for egen pass (judgment, ikke mekanisk).
- batch-processing-cost-reduction.md: batch-støttet modellsett febr→juni 2026
(gpt-5.1/gpt-5/o3/o4-mini/gpt-4.1-familien); API-versjon korrigert til v1 API.
50%-rabatt + 24h-turnaround urørt (re-verifisert current).
Begge: header→2026-06 + Source-header (folder inn Source-backfill).
Naming (Azure AI Foundry→Microsoft Foundry) urørt — egen pass (tema b).
validate 239/0, ms-ai-security 96/100. Ref-edits → judge-cache gyldig, kun re-score.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 20:34:45 +02:00
dd1036ab8a
fix(ms-ai-architect): Foundry URL-navnerom-migrering (ai-foundry → foundry/foundry-classic, 141 filer)
...
Task #5 del 1/3 (URL-migrering). Verifiseringen motbeviste STATE.md-premisset om ren prefix-swap: rebrand er per-URL, ikke mekanisk. En blind sed ai-foundry→foundry ville lagd 56 nye 404-er (classic-stiene finnes ikke under nytt foundry/-prefiks — bekreftet empirisk).
Metode: resolverte alle 237 unike KB-URLer mot live redirects (curl -L), bygde full-URL→full-URL-mapping fra faktisk url_effective. Bevarer locale-form, query (?view=) og #fragment per lenke.
- 231 navnerom-erstatninger over 141 filer (408 forekomster):
- 161 → azure/foundry/ (98 ren prefix-swap + 10 sti-reorg + reorg-tilfeller)
- 69 → azure/foundry-classic/ (eldre hub-spor: assistants, hub-DR, on-your-data; faktisk redirect-mål per operatorvalg)
- 1 → azure/foundry-local/
- 2 døde lenker (404) fikset til verifiserte mål:
- agent-service → azure/foundry/agents/overview
- concepts/evaluation-evaluators/ → azure/foundry/how-to/evaluate-generative-ai-app
- 5 path-/display-referanser (uten https://, i backticks/lenketekst) rettet manuelt.
- 6 slug-baserte ai-foundry-treff urørt (scope-grense): managed-grafana-dashboard, security-baseline, power-platform prompt-builder, architecture baseline-chat (sistnevnte slug-rebrand i annet navnerom — mulig fremtidig funn).
- Parkert til task #5 del 2/3: Norway East GPT-5-datasuverenitet-fiks + modellkatalog-utvidelse (5.3/5.4/5.5, gpt-oss, sora-2).
Verifisert: 0 gjenværende azure/ai-foundry/-navnerom i skills/. validate-plugin.sh 219 PASS. test-kb-integrity.sh 117/117 passed.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01REiKFhP4w6xGXXqWKpPCJJ
2026-06-18 13:37:06 +02:00
Kjell Tore Guttormsen
baa2d0220b
feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command
...
Add /ultraresearch-local for structured research combining local codebase
analysis with external knowledge via parallel agent swarms. Produces research
briefs with triangulation, confidence ratings, and source quality assessment.
New command: /ultraresearch-local with modes --quick, --local, --external, --fg.
New agents: research-orchestrator (opus), docs-researcher, community-researcher,
security-researcher, contrarian-researcher, gemini-bridge (all sonnet).
New template: research-brief-template.md.
Integration: --research flag in /ultraplan-local accepts pre-built research
briefs (up to 3), enriches the interview and exploration phases. Planning
orchestrator cross-references brief findings during synthesis.
Design principle: Context Engineering — right information to right agent at
right time. Research briefs are structured artifacts in the pipeline:
ultraresearch → brief → ultraplan --research → plan → ultraexecute.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-08 08:58:35 +02:00
