@heripo/research-radar 5.3.5 → 6.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -67,10 +67,10 @@ For academic publications:
67
67
  ## Installation
68
68
 
69
69
  ```bash
70
- npm install @heripo/research-radar '@llm-newsletter-kit/core@~3.0.6'
70
+ npm install @heripo/research-radar '@llm-newsletter-kit/core@~3.1.1'
71
71
  ```
72
72
 
73
- **Requirements**: Node.js 24.15.0 or newer within 24.x, or >= 26.0.0, and an ESM application. Node.js 25 is not supported. The package exports `dist/index.js` and TypeScript declarations (`dist/index.d.ts`), with a JavaScript sourcemap. The core engine is a peer dependency; the current supported range is `~3.0.6`. The floor moved to 3.0.6 because the 나라장터 target runs its triage inside a crawl fetch that core times out, and before 3.0.6 core classified a timeout as non-retryable, so that target failed on the first attempt every run. 3.0.5 remains required for the self-verification retry cap the generation prompt relies on.
73
+ **Requirements**: Node.js 24.15.0 or newer within 24.x, or >= 26.0.0, and an ESM application. Node.js 25 is not supported. The package exports `dist/index.js` and TypeScript declarations (`dist/index.d.ts`), with a JavaScript sourcemap. The core engine is a peer dependency; the current supported range is `~3.1.1`. Core 3.1.1 is required for recent-title guarding and source-grounded deadline extraction. It also includes the crawl-timeout retry handling and generation self-verification retry cap required by Radar.
74
74
 
75
75
  An OpenAI API key is always required and supplies all default models. The optional compatibility path for Anthropic or Google newsletter generation additionally requires that provider's key. Keys are passed explicitly to the library; load environment variables in your application.
76
76
 
@@ -149,6 +149,101 @@ All interfaces are exported from the package root and defined in [src/types/depe
149
149
 
150
150
  Candidate selection belongs to your repository. Persist `usedArticles` associations as needed to exclude previously published content. Issue numbering is initialized before the pipeline starts; coordinate concurrent runs in your application or database. `TaskService` tracks an active task within one service instance, not across processes or separate `generateNewsletter()` calls.
151
151
 
152
+ ### Recent titles and source deadlines
153
+
154
+ These APIs use the published core 3.1.1 package. The peer dependency requires
155
+ `~3.1.1`, and `npm ci` installs the locked package without a local core link.
156
+
157
+ - Implement optional `NewsletterRepository.findRecentPublishedTitles({ fromInclusive, toExclusive })`
158
+ to enable the title guard. Radar supplies the seven calendar days before the
159
+ publication date (exclusive). Return titles only from actually published issues
160
+ of the same newsletter/audience. Drafts and failed sends are excluded. The core
161
+ compares normalized titles and allows at most two title-only repairs.
162
+ - Pass `extractDeadlineOptions: {}` to extract deadlines during article analysis
163
+ with the importance model, or `{ model }` for a separate OpenAI ID/AI SDK model.
164
+ Persist `article.deadlines` in `updateAnalysis`: `[]` means extracted without
165
+ supported deadlines; `undefined` means not extracted/failed. Clear the cache
166
+ when the source changes. Omit the option to keep existing analysis calls.
167
+ - Add `includeEvents: true` to `extractDeadlineOptions` to also extract conference,
168
+ workshop and public site visit schedules. Registration cutoffs and attendance
169
+ dates are distinct entries. Events retain `type: 'event'`, start `date`/`time`,
170
+ and optional `endDate`/`endTime`; missing times are never invented.
171
+ The default remains deadline-only. Analysis preserves existing event caches
172
+ when the flag is disabled. Re-extract historical caches, including empty
173
+ arrays, when enabling events for previously analyzed articles.
174
+ - `extractResearchRadarDeadlines({ model, article: { title, detailContent } })`
175
+ provides the same original-source extraction for host-managed backfill and
176
+ verification. Pass `includeEvents: true` here and to
177
+ `refreshResearchRadarDeadlines()` to include events. It does not fetch URLs
178
+ or activate reminders.
179
+
180
+ The host activates reminders only after an article is actually included in a
181
+ published issue. Core's `usedArticles` is the candidate array, including articles
182
+ the editor may omit; it is not evidence of actual inclusion. The host selects
183
+ actually included articles from the preceding 60 days for the one-time backfill,
184
+ stores deadlines separately, and selects only imminent reminders for each issue.
185
+ Historical issue bodies are not passed into generation.
186
+
187
+ Before reminding, call `refreshResearchRadarDeadlines({ source: { title, url,
188
+ targetUrl }, model, customFetch?, publicDataApiKey? })`. It fetches the registered
189
+ detail through the same adapters and robots rules as crawling, with a 15-second
190
+ total network budget. Job APIs fetch one posting; 나라장터 queries only that
191
+ notice number's revisions and returns the latest revision's URL. No daily list,
192
+ triage, scoring or persistence runs. `fetchResearchRadarDeadlineSource()` is
193
+ available separately for source-only reads (`status: 'fetched'`).
194
+
195
+ Dates and times must match their verbatim evidence. Even an unchanged source
196
+ hash cannot reuse a cache that fails the current grounding rules; it is extracted
197
+ again. Unsupported values hold the reminder.
198
+
199
+ - `status: 'verified'` includes the fresh article, deadlines, `sourceHash`,
200
+ `checkedAt` and model usage. Explicit extensions use the new date; explicit
201
+ cancellations have `status: 'cancelled'`. Passing `previous: { sourceHash,
202
+ deadlines }` from a successful refresh skips extraction only if a fresh fetch
203
+ has the same hash and event extraction mode. Preserve the returned
204
+ `includeEvents` metadata in `previous`; absent metadata means deadline-only,
205
+ so enabling events forces extraction even if the source hash is unchanged.
206
+ Invalidate this cache when other extraction policy changes.
207
+ - `status: 'unverified'` includes a reason, without deadlines. Missing dates,
208
+ access failures, unsupported boards and extraction failures hold reminders;
209
+ they never cancel a stored action. Even a verified source does not confirm all
210
+ past actions: the host must match each action and hold unmatched ones. A
211
+ separate announcement at another URL is outside this targeted check.
212
+
213
+ Pass host-selected verified actions to
214
+ `renderVerifiedDeadlineReminders(reminders, publicationDate)` and place its result
215
+ in `templateOptions.deadlineRemindersMarkdown`. Today's and upcoming active
216
+ deadlines/events within seven days take priority; ongoing events through a known
217
+ end date fill any remaining slots. Each group is ordered by date and time, with
218
+ at most five entries overall. It preserves supplied periods and times
219
+ without inventing 23:59. The heading is **다가오는 일정·마감**. Today's entries say
220
+ **오늘 마감**, **오늘 개최** or **오늘 공개**, while ongoing events say **진행 중**.
221
+ An event's start time is not a cutoff: only its stated end time expires it during
222
+ the end date. Without an end date, it is listed only through its start date. The provider appends it to saved Markdown and HTML after
223
+ generation, so reminders add no LLM context. The host owns D-7/D-1 scheduling,
224
+ repeat suppression and publication history. Empty sections are omitted.
225
+
226
+ Prefer `templateOptions.verifiedDeadlineReminders` with freshly verified historical
227
+ actions. The provider merges these with source-grounded deadlines from articles
228
+ actually linked in the generated body, sorts them, and displays at most five
229
+ eligible deadlines/events in one linked section. Deduplication includes the
230
+ entry type, so a registration cutoff cannot replace an attendance schedule.
231
+ Event identity also includes the start/end dates and times, preserving separate
232
+ occurrences with the same title and kind. Deadline action deduplication is unchanged.
233
+ For a refreshed source,
234
+ only freshly verified actions are eligible: unmatched cached actions are held,
235
+ never inferred to be active or cancelled from free-form `title` or `kind` labels.
236
+ G2B revisions share a source identity by notice number. Pass each distinct action
237
+ as a freshly verified result to retain multiple actions from that source. Other
238
+ sources without supplied verification continue using grounded article deadlines.
239
+ The older
240
+ `deadlineRemindersMarkdown` option remains available for pre-rendered sections.
241
+ The generation prompt no longer produces a separate closing schedule list.
242
+ The colleague-sharing notice follows the highlighted schedule/deadline section
243
+ in both saved Markdown and HTML; no eligible entries means no empty section.
244
+ Set `templateOptions.shareNoticeMarkdown` to customize this notice in both
245
+ formats, omit it for the default, or pass an empty string to suppress it.
246
+
152
247
  ### Optional generation settings
153
248
 
154
249
  | Option | Behavior |
@@ -228,7 +323,7 @@ await generateNewsletter({
228
323
 
229
324
  The optional `contentGeneration: { provider, apiKey, model? }` compatibility path still supports Anthropic and Google for newsletter generation. `models.generateNewsletter` takes precedence when both are supplied. If `models.generateNewsletter` is omitted or `undefined`, the existing `contentGeneration` provider/model selection applies; without either option, generation uses `llmConfig.models.generateNewsletter`. `openAIApiKey` remains required even when supplying model objects for every stage.
230
325
 
231
- [src/config/index.ts](./src/config/index.ts) defines Korean output (`outputLanguage: '한국어'`), the cultural heritage domain (`expertField: ['문화유산']`), brand name, `subscribePageUrl`, LLM `maxRetries: 5`, chain `stopAfterAttempt: 3`, and generation `temperature: 0.3`. Publication settings are `minimumArticleCountForIssue: 5` and `priorityArticleScoreThreshold: 8`; the core engine evaluates them. In the locked core 3.0.6 implementation, the count check skips **5 or fewer** candidates unless at least one has importance score >= 8. An empty candidate list is always skipped.
326
+ [src/config/index.ts](./src/config/index.ts) defines Korean output (`outputLanguage: '한국어'`), the cultural heritage domain (`expertField: ['문화유산']`), brand name, `subscribePageUrl`, LLM `maxRetries: 5`, chain `stopAfterAttempt: 3`, and generation `temperature: 0.3`. Publication settings are `minimumArticleCountForIssue: 5` and `priorityArticleScoreThreshold: 8`; the core engine evaluates them. In the locked core 3.1.1 implementation, the count check skips **5 or fewer** candidates unless at least one has importance score >= 8. An empty candidate list is always skipped.
232
327
 
233
328
  ## Crawling targets and parsers
234
329
 
@@ -382,16 +477,18 @@ npm run health-check:proxy # Load the same .env and pass --proxy
382
477
  npm run health-check -- --skip-khs-excavation # Skip KHS excavation report/site-open targets
383
478
  ```
384
479
 
385
- **What it checks per target**:
480
+ **What it checks per crawling target**:
386
481
 
387
482
  - `parseList()`: Non-empty array; checks the first item for non-empty title/date and a detailUrl starting with `http`
388
483
  - `parseDetail()`: Fetches the first detail item and checks trimmed `detailContent` length >= 20
389
484
 
485
+ For the public-data APIs (ALIO, 나라일터, 나라장터), it sends the configured `PUBLIC_DATA_API_KEY` directly to each list endpoint with `numOfRows=1` and checks only for HTTP 200. 나라장터 probes both service and construction endpoints. Response bodies, result codes, list contents, and details are not validated. These three targets are skipped when the key is missing.
486
+
390
487
  Use repeatable `--skip-target=<id-or-name>` or `--skip-target <id-or-name>` to exclude targets by exact ID or name. `npm run health-check -- --help` lists options without crawling. This is a live-site smoke check of the first item per target, not full article validation; it does not invoke LLM analysis. The script exits with code 1 if any checked target fails.
391
488
 
392
489
  **Output**: Console table summary + compact text summary for CI integrations.
393
490
 
394
- **CI**: [.github/workflows/parser-health-check.yml](./.github/workflows/parser-health-check.yml) runs daily at 08:00 UTC (17:00 KST), or manually, on an `org-linux` runner with a 30-minute job timeout. It skips the two KHS excavation report/site-open targets. The health-check composes the same fetch as production — robots.txt gate, then the KRAS detail adapter — so disallowed boards are reported as skipped rather than failed: 16 skipped and 55 checked with the current configuration. The detail check tries up to three list items, so one unreadable post at the top of a board does not fail the target. Slack notifications require the `SLACK_BOT_TOKEN` secret and `SLACK_ALERT_DEV_CHANNEL` repository variable. Forks need a matching runner and notification configuration to use this workflow unchanged. The CLI also writes GitHub Actions outputs and a job summary when their environment variables are present.
491
+ **CI**: [.github/workflows/parser-health-check.yml](./.github/workflows/parser-health-check.yml) runs daily at 08:00 UTC (17:00 KST), or manually, on an `org-linux` runner with a 30-minute job timeout. It skips the two KHS excavation report/site-open targets. For crawling targets, the health-check composes the same fetch as production — robots.txt gate, then the KRAS detail adapter — so disallowed boards are reported as skipped rather than failed: 16 skipped and 55 checked with the current configuration. The detail check tries up to three list items, so one unreadable post at the top of a board does not fail the target. Slack notifications require the `SLACK_BOT_TOKEN` secret and `SLACK_ALERT_DEV_CHANNEL` repository variable. Forks need a matching runner and notification configuration to use this workflow unchanged. The CLI also writes GitHub Actions outputs and a job summary when their environment variables are present.
395
492
 
396
493
  ## 🤝 Contributing
397
494
 
package/dist/index.d.ts CHANGED
@@ -1,7 +1,16 @@
1
- import { UrlString, ParsedTarget, CrawlingTargetGroup, CrawlingTarget, UnscoredArticle, ArticleForUpdateByAnalysis, ArticleForGenerateContent, Newsletter, IsoDateString, AppLogger, EmailService, EmailMessage, PromptProvider, DateService as DateService$1, TaskService as TaskService$1, AnalysisProvider as AnalysisProvider$1, ContentGenerateProvider as ContentGenerateProvider$1, HtmlTemplate, CrawlingProvider as CrawlingProvider$1, GenerateNewsletterConfig } from '@llm-newsletter-kit/core';
2
- import { LanguageModel } from 'ai';
1
+ import { ArticleDeadline, UrlString, IsoDateString, ParsedTarget, CrawlingTargetGroup, CrawlingTarget, UnscoredArticle, ArticleForUpdateByAnalysis, ArticleForGenerateContent, Newsletter, AppLogger, EmailService, EmailMessage, PromptProvider, DateService as DateService$1, TaskService as TaskService$1, AnalysisProvider as AnalysisProvider$1, ContentGenerateProvider as ContentGenerateProvider$1, HtmlTemplate, CrawlingProvider as CrawlingProvider$1, GenerateNewsletterConfig, ExtractArticleDeadlinesConfig, ExtractArticleDeadlinesResult } from '@llm-newsletter-kit/core';
2
+ import { LanguageModel, LanguageModelUsage } from 'ai';
3
3
  import { OpenAIProvider } from '@ai-sdk/openai';
4
4
 
5
+ /** Host-selected, published action matched against a freshly verified source. */
6
+ interface VerifiedDeadlineReminder {
7
+ deadline: ArticleDeadline;
8
+ url: UrlString;
9
+ verificationStatus: 'verified';
10
+ }
11
+ /** Deterministic deadlines/events, no LLM context. Host owns selection and history. */
12
+ declare function renderVerifiedDeadlineReminders(reminders: VerifiedDeadlineReminder[], publicationDate: IsoDateString, now?: Date): string;
13
+
5
14
  /**
6
15
  * Repository interface for task management
7
16
  */
@@ -115,6 +124,18 @@ interface TagRepository {
115
124
  * Base template options shared by all newsletter variants.
116
125
  */
117
126
  interface BaseNewsletterTemplateOptions {
127
+ /**
128
+ * Deterministic reminder section from renderVerifiedDeadlineReminders().
129
+ * Appended to saved Markdown and HTML after generation; never fed to the LLM.
130
+ */
131
+ deadlineRemindersMarkdown?: string;
132
+ /** Freshly verified historical deadlines/events, merged with included articles. */
133
+ verifiedDeadlineReminders?: VerifiedDeadlineReminder[];
134
+ /**
135
+ * Custom colleague-sharing Markdown, placed after the unified deadline section
136
+ * in both saved Markdown and HTML. Omit for the default; use '' to suppress it.
137
+ */
138
+ shareNoticeMarkdown?: string;
118
139
  /**
119
140
  * Markdown content for KRAS news section.
120
141
  * Converted to HTML and injected into the newsletter template.
@@ -182,6 +203,15 @@ interface WelcomeTemplateOptions {
182
203
  * Repository interface for newsletter management
183
204
  */
184
205
  interface NewsletterRepository {
206
+ /**
207
+ * Titles of actually published issues in [fromInclusive, toExclusive).
208
+ * Scope the query to this newsletter/audience; exclude drafts and failed sends.
209
+ * Providing this method enables the preceding seven calendar days title guard.
210
+ */
211
+ findRecentPublishedTitles?(range: {
212
+ fromInclusive: IsoDateString;
213
+ toExclusive: IsoDateString;
214
+ }): Promise<string[]>;
185
215
  /**
186
216
  * Get the next issue order number
187
217
  * @returns Next issue order
@@ -266,6 +296,17 @@ interface NewsletterGeneratorDependencies {
266
296
  openAIApiKey: string;
267
297
  /** OpenAI model IDs or AI SDK model instances for every LLM task (optional). */
268
298
  models?: NewsletterModelConfig;
299
+ /**
300
+ * Opt in to original-article deadline extraction. An omitted model reuses the
301
+ * importance model; a string is resolved through the supplied OpenAI key.
302
+ * Repositories must persist deadlines, including an empty array. Omit to keep
303
+ * the existing analysis calls. This does not activate reminders on candidates.
304
+ */
305
+ extractDeadlineOptions?: {
306
+ model?: string | LanguageModel;
307
+ /** Include conferences, public site visits and other dated attendance opportunities. */
308
+ includeEvents?: boolean;
309
+ };
269
310
  /**
270
311
  * Non-OpenAI content generation configuration (optional).
271
312
  *
@@ -426,6 +467,9 @@ interface AnalysisModels {
426
467
  classifyTags: LanguageModel;
427
468
  analyzeImages: LanguageModel;
428
469
  determineImportance: LanguageModel;
470
+ extractDeadlines?: LanguageModel;
471
+ /** Event extraction is enabled only together with extractDeadlines. */
472
+ includeEvents?: boolean;
429
473
  }
430
474
  /**
431
475
  * Analysis provider implementation
@@ -441,6 +485,7 @@ declare class AnalysisProvider implements AnalysisProvider$1 {
441
485
  analyzeImagesOptions: {
442
486
  model: LanguageModel;
443
487
  };
488
+ extractDeadlineOptions?: AnalysisProvider$1['extractDeadlineOptions'];
444
489
  determineScoreOptions: {
445
490
  model: LanguageModel;
446
491
  minimumImportanceScoreRules: Array<{
@@ -476,13 +521,16 @@ declare class AnalysisProvider implements AnalysisProvider$1 {
476
521
  declare class ContentGenerateProvider implements ContentGenerateProvider$1 {
477
522
  private readonly articleRepository;
478
523
  private readonly newsletterRepository;
524
+ private readonly templateOptions?;
479
525
  private _issueOrder;
526
+ private readonly deadlineRemindersMarkdown;
480
527
  readonly model: LanguageModel;
528
+ readonly fetchRecentTitles?: ContentGenerateProvider$1['fetchRecentTitles'];
481
529
  /** HTML template with markers for title and content injection */
482
530
  htmlTemplate: HtmlTemplate;
483
531
  /** Newsletter brand name (defaults to config, can be overridden via constructor) */
484
532
  newsletterBrandName: string;
485
- constructor(model: LanguageModel, articleRepository: ArticleRepository, newsletterRepository: NewsletterRepository, templateOptions?: NewsletterTemplateOptions, brandName?: string);
533
+ constructor(model: LanguageModel, articleRepository: ArticleRepository, newsletterRepository: NewsletterRepository, templateOptions?: NewsletterTemplateOptions | undefined, brandName?: string);
486
534
  /** LLM temperature setting for content generation */
487
535
  temperature: number;
488
536
  /** Subscribe page URL */
@@ -685,5 +733,65 @@ declare const llmConfig: {
685
733
  */
686
734
  declare const researchRadarPromptProvider: PromptProvider;
687
735
 
688
- export { AnalysisProvider, ContentGenerateProvider, CrawlingProvider, DateService, TaskService, contentOptions, createCrawlingTargetGroups, generateNewsletter, generateWelcomeHTML, getSourceList, llmConfig, maximumImportanceScoreByDomain, newsletterConfig, researchRadarPromptProvider, robotsExemptOrigins };
689
- export type { ArticleRepository, ContentGenerationConfig, ContentOptions, ExcavationReport, ExcavationReportSource, NewsletterConfig, NewsletterGeneratorDependencies, NewsletterModelConfig, NewsletterRepository, NewsletterTemplateOptions, PreviewNewsletterOptions, SourceGroup, SourceItem, TagRepository, TaskRepository, WelcomeTemplateOptions };
736
+ type ResearchRadarDeadlineExtractionConfig = Omit<ExtractArticleDeadlinesConfig, 'outputLanguage'> & {
737
+ outputLanguage?: string;
738
+ };
739
+ /** Shared by host-managed backfill and targeted source verification. No DB writes. */
740
+ declare function extractResearchRadarDeadlines(config: ResearchRadarDeadlineExtractionConfig): Promise<ExtractArticleDeadlinesResult>;
741
+
742
+ interface ResearchRadarDeadlineSource {
743
+ title: string;
744
+ url: UrlString;
745
+ /** Original board URL retained when the article was collected. */
746
+ targetUrl: UrlString;
747
+ }
748
+ type DeadlineVerificationFailure = 'unsupported-source' | 'invalid-source-url' | 'source-unavailable' | 'empty-source' | 'no-supported-deadlines' | 'extraction-failed';
749
+ type FetchedSource = {
750
+ status: 'fetched';
751
+ article: {
752
+ title: string;
753
+ detailContent: string;
754
+ url: UrlString;
755
+ };
756
+ sourceHash: string;
757
+ checkedAt: string;
758
+ };
759
+ type UnverifiedSource = {
760
+ status: 'unverified';
761
+ reason: DeadlineVerificationFailure;
762
+ checkedAt: string;
763
+ };
764
+ type ResearchRadarDeadlineSourceResult = FetchedSource | UnverifiedSource;
765
+ type ResearchRadarDeadlineRefreshResult = (Omit<FetchedSource, 'status'> & {
766
+ status: 'verified';
767
+ deadlines: ArticleDeadline[];
768
+ /** Preserve this extraction scope when passing the result as previous. */
769
+ includeEvents?: boolean;
770
+ usage: LanguageModelUsage | undefined;
771
+ }) | UnverifiedSource;
772
+ interface ResearchRadarDeadlineSourceOptions {
773
+ source: ResearchRadarDeadlineSource;
774
+ customFetch?: typeof fetch;
775
+ publicDataApiKey?: string;
776
+ /** Total budget for the original page and parser API requests, not LLM calls. */
777
+ timeoutMs?: number;
778
+ }
779
+ type ResearchRadarDeadlineRefreshConfig = ResearchRadarDeadlineSourceOptions & Omit<ResearchRadarDeadlineExtractionConfig, 'article'> & {
780
+ /** Cache only a successful extraction from this source. A fresh fetch is mandatory. */
781
+ previous?: {
782
+ sourceHash: string;
783
+ deadlines: ArticleDeadline[];
784
+ /** Missing metadata denotes a legacy deadline-only extraction. */
785
+ includeEvents?: boolean;
786
+ };
787
+ };
788
+ /**
789
+ * Fetches only the registered detail source and any API requests its parser
790
+ * requires. Does not enumerate lists, look up existing URLs, score, or save.
791
+ */
792
+ declare function fetchResearchRadarDeadlineSource({ source, customFetch, publicDataApiKey, timeoutMs, }: ResearchRadarDeadlineSourceOptions): Promise<ResearchRadarDeadlineSourceResult>;
793
+ /** Only explicit, grounded results are verified. Missing dates are never cancellation. */
794
+ declare function refreshResearchRadarDeadlines(config: ResearchRadarDeadlineRefreshConfig): Promise<ResearchRadarDeadlineRefreshResult>;
795
+
796
+ export { AnalysisProvider, ContentGenerateProvider, CrawlingProvider, DateService, TaskService, contentOptions, createCrawlingTargetGroups, extractResearchRadarDeadlines, fetchResearchRadarDeadlineSource, generateNewsletter, generateWelcomeHTML, getSourceList, llmConfig, maximumImportanceScoreByDomain, newsletterConfig, refreshResearchRadarDeadlines, renderVerifiedDeadlineReminders, researchRadarPromptProvider, robotsExemptOrigins };
797
+ export type { ArticleRepository, ContentGenerationConfig, ContentOptions, DeadlineVerificationFailure, ExcavationReport, ExcavationReportSource, NewsletterConfig, NewsletterGeneratorDependencies, NewsletterModelConfig, NewsletterRepository, NewsletterTemplateOptions, PreviewNewsletterOptions, ResearchRadarDeadlineExtractionConfig, ResearchRadarDeadlineRefreshConfig, ResearchRadarDeadlineRefreshResult, ResearchRadarDeadlineSource, ResearchRadarDeadlineSourceOptions, ResearchRadarDeadlineSourceResult, SourceGroup, SourceItem, TagRepository, TaskRepository, VerifiedDeadlineReminder, WelcomeTemplateOptions };