Analyze remaining gaps after article type improvements; create and assign 4 follow-up issues

[Copilot]

All 8 article type improvement issues (#595–#602) were completed. Analyzed the current state of all generators, tests (2,026 passing), and workflow files to identify remaining technical debt.

Findings

• Hardcoded riksmöte '2025/26' in 3 generators (8 instances) — will break at September 2026 session boundary
  • weekly-review.ts (4 places) — already imports getCurrentRiksmote but only uses it in Step 6
  • monthly-review.ts (3 places) — no import at all
  • propositions.ts (1 place) — no import at all
• All 10 agentic workflow .md prompts hardcode rm: "2025/26" in MCP query examples
• Outdated TODO in committee-reports.ts:78 references tools that are already implemented
• No test enforcement — existing test documents hardcoding rather than preventing it

Issues Created & Assigned to Copilot

Issue	Priority	PR	What
#633	HIGH	#639	Replace hardcoded riksmöte with getCurrentRiksmote() in 3 generators
#635	MEDIUM	#637	Add dynamic riksmöte instructions to 10 workflow prompts
#636	MEDIUM	#640	Add regression test preventing hardcoded riksmöte
#634	LOW	#638	Remove stale TODO in committee-reports.ts

Reference pattern (already correct in motions.ts:234):

export function getCurrentRiksmote(date: Date = new Date()): string {
  const year = date.getFullYear();
  const month = date.getMonth(); // 0-based; September = 8
  const startYear = month >= 8 ? year : year - 1;
  return `${startYear}/${String(startYear + 1).slice(-2)}`;
}

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json