refactor(fiction-assistance)!: reduce to portable guidance and analysis (v2.0.0)

Strip the Universalis-specific vault layout and card-management
machinery. The plugin is now a general-purpose fiction toolkit:
nine commands that take a manuscript path/glob/selection via
\$ARGUMENTS and write their output to the conversation.

Surviving commands, flattened into commands/:
- analyze-story: structural and statistical analysis
- bechdel-test: representation tests (Bechdel + related)
- check-continuity: plot/character/world continuity
- check-voice: per-character voice consistency
- developmental-review: structural feedback on a scene/chapter
- extract-research: world-building and research inventory
- final-review: synthesis of prior-phase reviews
- generate-timeline: chronology with consistency checks
- strategic-review: craft-based critique with priority ranking

Removed (vault and card management): 10 update-*-cards commands,
cleanup-generated, update-changed, update-links,
update-chapter-summaries, validate-story, validate-pdf, score-scenes.
The original bespoke command set is preserved in 65c29d7 for recovery.

Agent (line-editor) and skill (reviewing-fiction) were already
portable and are unchanged. plugin.json no longer needs the
commands subdirectory paths since the layout is flat. Marketplace
description updated to reflect the general-purpose scope.

BREAKING CHANGE: All update-*-cards, cleanup-generated, update-changed,
update-links, update-chapter-summaries, validate-story, validate-pdf,
and score-scenes commands are removed. perform-bechdel-tests is renamed
to bechdel-test. review-final is renamed to final-review.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

fiction-assistance/commands/generate-timeline.md

@@ -0,0 +1,39 @@
+---
+description: Build a chronological timeline from a manuscript's events
+argument-hint: "[path, glob, or selection]"
+allowed-tools: [Read, Glob, Grep]
+---
+
+Read the material at `$ARGUMENTS` and construct a chronological timeline of events. The result is a reference document the writer can use to spot inconsistencies and ground future revisions.
+
+## What to extract
+
+For each event of plot significance, capture:
+
+- **Event** — what happens, in one sentence
+- **When** — absolute date/time if given, otherwise relative timing ("the morning after X", "three days before the inciting incident")
+- **Duration** — if the event takes more than a moment
+- **Characters involved**
+- **Location**
+- **Source** — chapter/scene where this is established
+- **Significance** — major plot point, minor beat, background
+
+Include events from any era the text references — pre-story backstory, on-page action, and any post-story implications mentioned in epilogue or dialogue.
+
+## Output format
+
+Three sections:
+
+### 1. Backstory timeline
+Events that happened before the story opens, in chronological order. Include character histories and world events the text references.
+
+### 2. Story timeline
+On-page events, in chronological order (not necessarily the order they're presented in the text). Note where the narrative diverges from chronology — flashbacks, parallel scenes, time-jumps.
+
+### 3. Consistency issues
+- **Contradictions** — A happens before B in one place and after in another
+- **Impossibilities** — character in two places at once, travel times that don't add up
+- **Gaps** — unexplained jumps in character or plot timeline
+- **Vague spots** — events where the timing is ambiguous and should be firmed up
+
+Format the timelines as Markdown lists or tables. Cite chapters/scenes for every entry. Keep entries to one or two sentences each.