4d773d6ee8
Moved out (kept outside the repo, in the team's internal tracker): - AGENT-BRIEF.md: operating rules for the team's own agents - documentation/slide-deck-outline.md, documentation/README-longform.md: internal pitch material; the README and why.md cover the same ground - plugin-designs/gospel-resources/SOURCES-CHECKED-AND-REJECTED.md: research log - .claude/ (an editor status line), .forgejo/ (a CI workflow that never ran), _archive/ (a retired staging page; already gitignored but still tracked) Seven code comments that named these files now describe the rule instead. Fixed five dead links left from the docs/ -> documentation/ move, including the one in template-bundle that every new plugin inherits. The delegation diagram now shows the whole model: the Plugin Studio with the shared library and the merge queue into main, seven production plugins with capability badges and the Experimental shelf, one agent per plugin (a roaming agent for the shelf), the shepherd's oversight ring, a legend, and the five ways a build ships.
41 lines
1.9 KiB
JavaScript
41 lines
1.9 KiB
JavaScript
/**
|
|
* @map — public surface re-exports.
|
|
*
|
|
* Convention: bundles import from this barrel for the most-used pieces, OR
|
|
* subpath-import from '@map/components/X.vue' / '/composables/Y.js'
|
|
* etc. for surgical imports that tree-shake more cleanly.
|
|
*
|
|
* Add re-exports as `map-core` grows during migration. Keep this file thin —
|
|
* a fat barrel kills tree-shaking. Subpath imports are preferred.
|
|
*/
|
|
|
|
// Components — populated during migration-001+
|
|
// export { default as SemanticTreeLegend } from './components/legends/SemanticTreeLegend.vue'
|
|
// export { default as PeopleGroupDetail } from './components/PeopleGroupDetail.vue'
|
|
|
|
// Composables — populated during migration-001+
|
|
// export { useMapData } from './composables/useMapData.js'
|
|
// export { useMapLayers } from './composables/useMapLayers.js'
|
|
// export { useEntitySearch } from './composables/useSearch.js'
|
|
|
|
// Colors — the old monolith shims (colorStrategies.js / colors.js /
|
|
// prayerColors.js) are retired (removed from the library). Import the
|
|
// real modules directly: './colors/_registry.js' (COLOR_MODES,
|
|
// getColorStrategy, buildColorExpression), './colors/language-family.js',
|
|
// './colors/engagement.js', './colors/adoption.js', './colors/prayer-progress.js'.
|
|
// export * from './colors/_registry.js'
|
|
|
|
// Utils — populated during migration-001+
|
|
// export { default as DataSourceManager } from './utils/DataSourceManager.js'
|
|
|
|
// Stores — Pinia stores live at './stores/<name>.js' and are intentionally NOT
|
|
// re-exported here. Bundle entries should subpath-import them as
|
|
// `@map/stores/dataStore.js` (or mapStore / uiStore) for tree-shaking
|
|
// reasons. Keeping this barrel thin avoids pulling pinia into bundles that
|
|
// don't need it.
|
|
|
|
// Data lookup tables — JSON in './data/' (e.g. langFamilyByLanguage.json) —
|
|
// subpath-import as `@map/data/langFamilyByLanguage.json`. Not
|
|
// re-exported (would force JSON into the barrel chunk).
|
|
|
|
export const MAP_CORE_VERSION = '0.1.0'
|