star-freight 1.0.1__tar.gz

star_freight-1.0.1/.github/workflows/ci.yml

@@ -0,0 +1,59 @@
+name: CI
+
+on:
+  push:
+    paths:
+      - "src/**"
+      - "tests/**"
+      - "pyproject.toml"
+      - ".github/workflows/**"
+  pull_request:
+    paths:
+      - "src/**"
+      - "tests/**"
+      - "pyproject.toml"
+      - ".github/workflows/**"
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev,tui]"
+
+      - name: Run tests
+        run: |
+          python -m pytest tests/ -x -q --ignore=tests/test_tui_voyage_legacy.py
+
+      - name: Run tests with coverage (3.12 only)
+        if: matrix.python-version == '3.12'
+        run: |
+          python -m pytest tests/ --cov=src/portlight --cov-report=xml --ignore=tests/test_tui_voyage_legacy.py
+
+      - name: Upload coverage
+        if: matrix.python-version == '3.12'
+        uses: codecov/codecov-action@v5
+        with:
+          file: coverage.xml
+          fail_ci_if_error: false
+
+      - name: Maritime term guard
+        run: |
+          python -m pytest tests/test_maritime_guard.py -v

star_freight-1.0.1/.github/workflows/pages.yml

@@ -0,0 +1,50 @@
+name: Deploy site to GitHub Pages
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'site/**'
+      - '.github/workflows/pages.yml'
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - name: Install site dependencies
+        working-directory: site
+        run: npm ci
+
+      - name: Build site
+        working-directory: site
+        run: npm run build
+
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site/dist
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

star_freight-1.0.1/.github/workflows/publish.yml

@@ -0,0 +1,33 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tools
+        run: python -m pip install --upgrade pip build
+
+      - name: Build wheel + sdist
+        run: python -m build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

star_freight-1.0.1/.gitignore

@@ -0,0 +1,12 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+dist/
+build/
+*.egg-info/
+saves/
+.venv/
+site/.astro/
+site/dist/
+site/node_modules/
+.polyglot-cache.json

star_freight-1.0.1/ACCEPTANCE_CRITERIA.md

@@ -0,0 +1,110 @@
+# Acceptance Criteria — Star Freight
+
+> Derived directly from the 3 GDOS Proof Artifacts.
+> These are not vague goals — they are explicit pass/fail conditions.
+> The vertical slice ships when all three pass.
+
+---
+
+## Proof 1: Golden Path
+
+**Tests:** The game feels like one captain's life, not three stacked systems.
+
+### Pass conditions:
+
+1. **Continuous session:** A 15–30 minute play session flows through trade, combat, culture, and narrative without hard mode switches or menu-wall transitions.
+
+2. **Pressure creates movement:** The player takes a contract not because it's the "next quest" but because crew pay is due, ship needs fuel, or a debt is closing in.
+
+3. **Trade feeds tactics:** A trade decision (accepting a risky route, carrying contraband, docking at a hostile station) directly creates or modifies a combat encounter.
+
+4. **Tactics feed plot:** A combat outcome (victory, loss, retreat) changes reputation, opens or closes a narrative lead, or shifts faction standing.
+
+5. **Plot feeds trade:** An investigation lead or narrative event changes which stations are safe, which goods are valuable, or which contacts are available.
+
+6. **Crew matters:** At least one moment where having a specific crew member changes available options (trade access, combat ability, cultural knowledge, or narrative lead).
+
+7. **State change:** The player ends the session in a measurably different campaign state: different credits, reputation, crew condition, knowledge, obligations, or investigation progress.
+
+### Fail conditions:
+
+- Any system feels decorative (can be ignored without consequence)
+- Combat can be avoided entirely with no tradeoff
+- Trade is just "buy low, sell high" disconnected from narrative
+- Plot feels like a separate quest log
+- Crew members are interchangeable stat buffs
+
+---
+
+## Proof 2: Encounter
+
+**Tests:** Combat is a campaign event, not a detached tactics minigame.
+
+### Pass conditions:
+
+1. **Causal origin:** The encounter exists because of a trade decision, faction standing, bounty status, contract obligation, or investigation pursuit — not random spawn.
+
+2. **Crew binding active:** At least one tactical option exists only because a specific crew member is present, and at least one option is unavailable because a crew member is absent or injured.
+
+3. **Cultural context:** Cultural knowledge affects at least one of: whether combat starts, deployment setup, available surrender terms, reinforcement likelihood, salvage legality, or reputation consequences.
+
+4. **Three valid outcomes:** Victory, loss, and retreat all produce distinct and interesting campaign state changes.
+
+   - **Victory:** Not just "credits and loot." Reputation shift, faction standing change, potential crew injury, investigation lead, or new obligation.
+   - **Loss:** Not "reload." Cargo seized, crew injured, ship damaged, forced to a specific station, reputation hit, debt incurred.
+   - **Retreat:** Not "free escape." Fuel/supply cost, reputation as coward, contract failure, route now dangerous, crew morale hit.
+
+5. **Compact resolution:** 5–8 turns. If it takes longer, the design is wrong.
+
+6. **Aftermath feeds loop:** After the encounter, the player's next trade/route/contract decision is materially different than it would have been before the fight.
+
+### Fail conditions:
+
+- Combat feels like a random interruption
+- Crew members don't change tactical options
+- All three outcomes feel the same (just different numbers)
+- The player can ignore encounters without consequence
+- Encounter takes more than 10 turns regularly
+
+---
+
+## Proof 3: Economy
+
+**Tests:** Pressure remains meaningful over repeated runs and different captain styles.
+
+### Pass conditions:
+
+1. **Early squeeze:** Hours 1–2 feel tight. The player cannot ignore crew pay, maintenance, or fuel. Contracts are taken out of need, not preference.
+
+2. **First momentum:** By hour 3–4, the player has made enough decisions that their captain has a visible economic identity: a preferred route, a trusted contact, a known culture, a recurring risk.
+
+3. **Viable paths:** Legal (merchant), gray (opportunist), and predatory (pirate) play are all economically sustainable. None is obviously dominant.
+
+4. **Setback recovery:** After a major loss (ship damage, cargo seizure, crew injury), recovery takes 2–4 play sessions, costs something real (dignity, time, leverage, or future options), and creates new decisions rather than dead air.
+
+5. **Late pressure:** By hour 6–8, the player has more capability but also more obligations. Pressure has changed shape (from survival to strategy) but not disappeared.
+
+6. **No chores:** Crew pay and maintenance create route/contract/allegiance decisions, not repetitive busywork. The player feels squeezed into choices, not squeezed into grind.
+
+7. **Anti-soft-lock:** A player who makes bad decisions can always recover. Recovery is ugly, slow, and interesting — never painless, never impossible.
+
+8. **Income curve:** Starting income ~200–400cr/run. By hour 6–8, income ~2000–4000cr/run. Growth comes from better routes, crew capability, cultural access, and reputation — not just bigger numbers.
+
+### Fail conditions:
+
+- Player can grind one safe route forever without pressure
+- Gray/pirate play is either broken or obviously dominant
+- Setbacks create dead time (nothing to do while recovering)
+- Late game has no pressure (player is rich and safe)
+- Anti-soft-lock mechanism is invisible or breaks the economy
+- Crew pay feels like a tax instead of a decision driver
+
+---
+
+## Verification Protocol
+
+Each proof is verified by playing the game (or running a deterministic test harness) and checking every pass condition. A proof passes when ALL conditions are met. A proof fails if ANY fail condition is triggered.
+
+The vertical slice (Phase 6) ships when all three proofs pass.
+
+No proof is "close enough." Either the loop works or it doesn't.

star_freight-1.0.1/BUILD_PLAN.md

@@ -0,0 +1,161 @@
+# Build Plan — Star Freight
+
+> Phase 0 is complete when the fork runs, the seams are mapped, and the build order is locked.
+> Production phases are ordered by thesis risk, not feature completeness.
+
+---
+
+## Phase 0: Fork Truth (current)
+
+**Goal:** Inherit Portlight, prove the fork runs, map every inherited vs new system.
+
+- [x] Create repo (mcp-tool-shop-org/star-freight)
+- [x] Copy Portlight source, tests, world data
+- [x] Update pyproject.toml for Star Freight
+- [x] Write FORK_MAP.md (inherited vs replaced vs new vs removed)
+- [ ] Write ACCEPTANCE_CRITERIA.md (proof-derived pass conditions)
+- [ ] Write STATE_MODEL.md (code-facing canonical state)
+- [ ] Verify inherited tests pass (`pytest`)
+- [ ] Initial commit and push
+- [ ] Strip removed modules (printandplay, medieval weapons/armor, fleet)
+- [ ] Verify tests still pass after strip
+
+**Exit condition:** Fork runs green. Every system is tagged inherited/replace/new/remove. Build order is locked.
+
+---
+
+## Phase 1: Crew Binding Spine
+
+**Goal:** Build the thesis seam. Crew members are the binding constraint across trade, tactics, and narrative.
+
+**Why first:** If crew binding is weak, the game becomes three stacked systems. This is the single highest-risk design decision.
+
+- [ ] Design crew data model (identity, abilities, cultural knowledge, loyalty, fitness, ship role)
+- [ ] Implement crew roster management (recruit, dismiss, injury, recovery)
+- [ ] Wire crew to trade (cultural access, negotiation modifiers, merchant relationships)
+- [ ] Wire crew to combat (abilities determined by crew, absence limits options)
+- [ ] Wire crew to narrative (crew unlock plot leads, cultural knowledge gates)
+- [ ] Wire crew to ship (engineer → repair ability, gunner → weapon power, pilot → evasion)
+- [ ] Crew morale and pressure (pay, injury, loyalty shifts, departure risk)
+- [ ] Tests for all crew bindings
+
+**Exit condition:** Adding/removing a crew member visibly changes trade options, combat abilities, and narrative access in a test harness.
+
+---
+
+## Phase 2: Grid Combat Engine
+
+**Goal:** One tactical combat system that works for ground encounters and ship battles.
+
+**Why second:** Combat is the second most visible system. It must be unified before content.
+
+- [ ] Grid model (hex or square, obstacles, cover, positioning)
+- [ ] Turn system (initiative, action points, move/attack/ability/item)
+- [ ] Ground combat entities (crew as combatants, enemy archetypes)
+- [ ] Ship combat entities (ships-as-characters, same grid, bigger numbers)
+- [ ] Crew abilities wired to combat (determined by crew binding spine)
+- [ ] Victory/loss/retreat with real state consequences
+- [ ] Boarding transition (ship combat → ground combat mid-encounter)
+- [ ] Encounter state machine (replaces Portlight's 4-phase escalation)
+- [ ] Combat views (TUI grid renderer)
+- [ ] Tests: full encounter with state change verification
+
+**Exit condition:** Can play a ship encounter that transitions to boarding, with crew abilities active, and aftermath changes campaign state.
+
+---
+
+## Phase 3: Cultural Knowledge System
+
+**Goal:** Civilizations feel alive and knowledge matters mechanically.
+
+- [ ] Cultural knowledge model (per-civilization understanding level)
+- [ ] Knowledge gates (trade access, diplomatic options, safe passage, ritual participation)
+- [ ] Knowledge acquisition (crew members, time in culture, cultural events, study)
+- [ ] Customs and consequences (violate customs → reputation damage, respect them → access)
+- [ ] Civilization-specific mechanics (Keth seasons, Veshan debt, Orryn drift markets, Sable Reach silence protocols)
+- [ ] Tests: cultural knowledge changes available options at a station
+
+**Exit condition:** Player with Keth crew member can access Keth seasonal markets that a culturally ignorant player cannot.
+
+---
+
+## Phase 4: Investigation System
+
+**Goal:** The conspiracy plot layer that gives the campaign its arc.
+
+- [ ] Investigation state (leads, evidence, connections, dead ends)
+- [ ] Lead acquisition (crew contacts, station events, trade encounters, faction relationships)
+- [ ] Evidence gates (investigation progress unlocks plot beats)
+- [ ] Investigation cost (time, reputation, money — the plot competes with survival)
+- [ ] 10 investigation beats mapped to campaign progression
+- [ ] Tests: investigation progress changes available narrative and gameplay options
+
+**Exit condition:** Investigation feels like a real campaign thread with economic and political cost, not a separate quest log.
+
+---
+
+## Phase 5: Content Rewrite
+
+**Goal:** Replace all Portlight content with Star Freight world.
+
+- [ ] 5 civilizations fully defined in code (from Content Architecture)
+- [ ] 20 stations (4 per civ) with markets, services, cultural rules
+- [ ] Space lanes between stations with distance, risk, encounter tables
+- [ ] 20 trade goods with civilization affinities
+- [ ] Ship classes (sci-fi vessels replacing sailing ships)
+- [ ] 7 crew members with full identity, abilities, cultural knowledge, loyalty arcs
+- [ ] Contract families reskinned for sci-fi
+- [ ] Encounter tables (pirates, patrols, faction conflicts, hazards)
+- [ ] Station NPCs with cross-station relationships
+- [ ] Transit events (replacing sea culture)
+
+**Exit condition:** Portlight maritime content fully replaced. No medieval language, no ocean references, no sailing terminology in gameplay.
+
+---
+
+## Phase 6: Vertical Slice
+
+**Goal:** Prove the three-layer loop works end to end.
+
+- [ ] 5 stations (one per civ), 8 lanes, 5 trade goods
+- [ ] 2 crew members recruited and wired
+- [ ] 3 contract types available
+- [ ] At least 1 ground combat and 1 ship combat encounter
+- [ ] Cultural knowledge check at 1 station
+- [ ] 1 investigation lead discoverable
+- [ ] Economy runs for ~30 minutes of play without collapse
+- [ ] All 3 acceptance criteria pass
+
+**Exit condition:** Golden Path, Encounter, and Economy proofs all pass as playable sequences.
+
+---
+
+## Phase 7: Full Build
+
+**Goal:** Scale from vertical slice to full game.
+
+- [ ] All 20 stations live
+- [ ] All 7 crew members recruitable
+- [ ] Full investigation chain (10 beats)
+- [ ] All 5 civilization cultural mechanics active
+- [ ] Balance harness adapted and running
+- [ ] Stress harness extended with new invariants
+- [ ] Full playthrough possible: disgrace → merchant/pirate → resolution
+
+**Exit condition:** The full designed game is playable. GDOS Thesis Lock is honored.
+
+---
+
+## Build Order Law
+
+The order above is not arbitrary. It follows thesis risk:
+
+1. **Crew binding** — if this fails, no game
+2. **Combat** — if this is boring, players leave
+3. **Culture** — if this is shallow, the world is dead
+4. **Investigation** — if this is missing, no campaign arc
+5. **Content** — if this is wrong, it can be rewritten
+6. **Slice** — proof of integration
+7. **Full** — scale
+
+Never skip ahead. Never build content before systems. Never build systems before the thesis seam.

star_freight-1.0.1/CHANGELOG.md

@@ -0,0 +1,47 @@
+# Changelog
+
+All notable changes to Star Freight are documented here.
+
+## [1.0.0] - 2026-03-24
+
+### Added
+- Complete game engine: crew binding, grid combat, cultural knowledge, investigation
+- Campaign integration layer wiring all four system truths
+- 3 expansion packs: Working Lives, Houses/Audits/Seizures, Shortages/Sanctions/Convoys
+- 3 proved captain paths: Relief/Legitimacy, Gray/Document, Honor/Frontier
+- 10 TUI view functions rendering from campaign state
+- Star Freight TUI surface (StarFreightApp) with void palette
+- Captain pressure bar (persistent header)
+- Maritime term guard CI test (12 assertions)
+- Dogfood system: 12-scenario matrix, 3 waves completed
+- P1 economy tuning: credit ratio 4.78x (target 3-5x)
+- Fear classifier: 3/3 distinct captain fears
+- Scenario override system: danger_multiplier, initial_state support
+- README in 8 languages, HANDBOOK as operating manual
+
+### Changed
+- TUI cutover from Portlight (maritime) to Star Freight (space)
+- App class: PortlightApp -> StarFreightApp
+- Theme: ocean palette -> void palette
+- Currency: silver -> credits (₡)
+- Navigation: 12 maritime tabs -> 8 Star Freight tabs
+- Station services: "shipyard" -> "drydock"
+
+### Fixed
+- Scenario overrides now applied before simulation (not after)
+- simulate_run respects starting station from initial_state
+- Honor escalation stress now actually stresses (was mislabeled baseline)
+
+## [0.1.1-dogfood] - 2026-03-24
+
+### Fixed
+- P1 tuning confirmed under corrected scenario infrastructure
+- Wave 3: 8/8 pass criteria met
+
+## [0.1.0-dogfood] - 2026-03-23
+
+### Added
+- Initial dogfood release
+- GDOS game design framework
+- All four system truth modules
+- Wave 1 and Wave 2 dogfood runs

star_freight-1.0.1/FORK_MAP.md

@@ -0,0 +1,105 @@
+# Fork Map — Star Freight ← Portlight
+
+> What we inherited, what we keep, what we replace, what we build new.
+> This is the single source of truth for fork decisions.
+
+---
+
+## Inherited Intact (use as-is, reskin content only)
+
+These systems are architecturally sound and map directly to the sci-fi setting.
+
+| Portlight Module | Star Freight Role | Notes |
+|---|---|---|
+| `engine/economy.py` | Trade engine | Scarcity-ratio pricing, stock mutation, buy/sell receipts — identical mechanic, different goods |
+| `engine/voyage.py` | Travel engine | Depart/advance/arrive state machine — "sailing" becomes "transit between stations" |
+| `engine/contracts.py` | Contract system | 7 contract families map cleanly (procurement, smuggling, reputation charter, etc.) |
+| `engine/reputation.py` | Reputation engine | Regional standing + commercial trust + decay — per-civilization instead of per-region |
+| `engine/infrastructure.py` | Station services | Warehouses, broker offices, credit lines, insurance — rename, keep mechanics |
+| `engine/models.py` | Core state schema | Dataclass foundation — extend, don't replace |
+| `engine/save.py` | Save/load | JSON serialization — extend for new state |
+| `engine/port_arrival_engine.py` | Station arrival | Dock → pay fee → refresh prices → offers — same flow |
+| `engine/captain_identity.py` | Captain background | 9 archetypes → rework for military pilot backstory variants |
+| `engine/narrative.py` | Milestone engine | Campaign milestone evaluation — extend for investigation |
+| `engine/campaign.py` | Campaign state | Arc tracking, unlocks, victory conditions — extend |
+| `engine/underworld.py` | Pirate factions | Faction standing, hostility — rename factions to sci-fi |
+| `engine/loot.py` | Salvage/loot | Post-encounter drops — reskin |
+| `balance/` | Balance harness | Seed-deterministic simulation with policy bots — invaluable, keep whole |
+| `stress/` | Stress harness | Invariant checking per tick — keep, extend invariants |
+| `receipts/` | Trade ledger | Deterministic receipt hashing — keep intact |
+
+## Must Be Replaced (same role, new implementation)
+
+| Portlight Module | Why Replace | Star Freight Replacement |
+|---|---|---|
+| `engine/combat.py` | Stance-triangle melee doesn't fit sci-fi grid combat | New: grid-based tactical combat (shared for ground + ship) |
+| `engine/duel.py` | Sword duel orchestrator — no equivalent in sci-fi | Remove entirely |
+| `engine/naval.py` | Broadside/close/evade — ship combat is now grid combat with ships-as-characters | Replace with unified grid engine |
+| `engine/encounter.py` | 4-phase naval escalation — replace with encounter → grid combat (ground or ship) | New encounter state machine |
+| `engine/skill_engine.py` | Medieval skill tree — replace with crew ability system | New: crew binding spine |
+| `engine/companion_engine.py` | Simple morale + role bonus — too thin for crew-as-binding-constraint | New: deep crew system (tactical + cultural + narrative) |
+| `engine/culture_engine.py` | Sea culture flavor injection — replace with civilization knowledge system | New: cultural knowledge engine |
+| `engine/sea_culture_engine.py` | Voyage-day flavor — replace with transit encounter system | New: transit event engine |
+| `engine/injuries.py` | Personal injury tracking — extend to crew + ship damage model | New: unified damage/repair |
+| `engine/hunting.py` | Forage/hunt at port — no direct equivalent | Remove or rethink as salvage ops |
+| `engine/weapon_quality.py` | Melee weapon condition — no equivalent | Remove |
+| `engine/weapon_provenance.py` | Weapon pedigree — no equivalent | Remove |
+| `app/combat_views.py` | Duel rendering — replace with grid combat UI | New: grid combat renderer |
+| `app/tui/screens/combat.py` | Stance selection screen — replace | New: tactical grid screen |
+| `app/tui/screens/encounter.py` | Naval encounter flow — replace | New: encounter screen |
+
+## Must Be Built New (no Portlight equivalent)
+
+| System | Design Doc Source | Priority |
+|---|---|---|
+| **Crew Binding Spine** | System Laws §Crew | **P0 — thesis seam** |
+| **Grid Combat Engine** | System Laws §Combat | P1 — shared ground/ship |
+| **Cultural Knowledge System** | System Laws §Cultural Knowledge | P2 — civilization depth |
+| **Investigation System** | System Laws §Investigation | P3 — conspiracy plot layer |
+| **Civilization Content** | Content Architecture (5 civs) | P1 — parallel with systems |
+| **Ship-as-Character Model** | System Laws §Combat | P1 — unified with grid |
+| **Debt Ledger (Veshan)** | Progression Economy §Veshan | P2 — civ-specific pressure |
+| **The Telling (Keth)** | Content Architecture §Keth | P2 — civ-specific ritual |
+| **Transit Events** | Experience Contract §sub-loop | P2 — replaces sea culture |
+
+## Remove (Portlight-specific, no Star Freight equivalent)
+
+| Module | Reason |
+|---|---|
+| `printandplay/` | Board game generator — not applicable |
+| `content/melee_weapons.py` | Medieval weapons |
+| `content/ranged_weapons.py` | Medieval ranged |
+| `content/armor.py` | Medieval armor |
+| `content/fighting_styles.py` | Regional sword traditions |
+| `content/sea_culture.py` | Maritime flavor text — replaced by civilization culture |
+| `content/port_institutions.py` | Mediterranean institutions |
+| `content/port_institutions_east.py` | East Indies institutions |
+| `engine/fleet.py` | Multi-ship management (planned, never active) |
+| All `world/ports/*.json` | Maritime port data — replaced by station data |
+
+## Content Reskin (keep structure, replace data)
+
+| Content Module | Reskin Target |
+|---|---|
+| `content/ports.py` | 20 ports → 20 stations (4 per civilization) |
+| `content/routes.py` | 65 sea routes → space lanes between stations |
+| `content/goods.py` | 35 maritime goods → 20 sci-fi trade goods |
+| `content/ships.py` | 5 ship classes → sci-fi vessel classes |
+| `content/seasons.py` | 4 seasons → Keth seasonal cycle or remove |
+| `content/companions.py` | 15 companions → 7 crew members (deeper) |
+| `content/merchants.py` | Merchant archetypes → station vendor types |
+| `content/factions.py` | 8 pirate factions → sci-fi criminal/rival factions |
+| `content/contracts.py` | Contract templates → sci-fi contract families |
+| `content/skills.py` | 10 skills → crew abilities |
+| `content/upgrades.py` | Ship upgrades → sci-fi ship modules |
+| `content/crew_roles.py` | Crew roles → Star Freight crew roles |
+
+---
+
+## Fork Rules
+
+1. **Inherit first.** Don't rewrite working systems that map cleanly.
+2. **Portlight is not sacred.** Anything that fights the sci-fi captain fantasy is provisional.
+3. **One combat engine.** Grid-based, shared between ground and ship. No mode split.
+4. **Crew is the new seam.** The companion system must be rebuilt from scratch — it's the thesis.
+5. **Content is the last step.** Systems first, then stations/goods/NPCs.