Summary
specfact code import currently scans hidden and heavyweight artifact trees before ignore rules take effect, which inflates runtime on real repositories and produces misleading ETA feedback because skipped files still count toward totals. The same runtime area also references project-bundle Jinja2 templates that are missing from the packaged module artifact, so installed workflows can fail even when commands are present.
Change
OpenSpec change: openspec/changes/codebase-import-runtime-hardening/
Scope
packages/specfact-project — shared import ignore policy, .specfact/.specfactignore, large-artifact warnings, dynamic ETA/progress, generator template packagingpackages/specfact-codebase — import command/runtime alignment
Capabilities
- New:
codebase-import-runtime
- Modified:
bundle-packaged-resources
Parent Feature
Part of #234 — [Feature] Code Import Runtime Hardening
Summary
specfact code importcurrently scans hidden and heavyweight artifact trees before ignore rules take effect, which inflates runtime on real repositories and produces misleading ETA feedback because skipped files still count toward totals. The same runtime area also references project-bundle Jinja2 templates that are missing from the packaged module artifact, so installed workflows can fail even when commands are present.Change
OpenSpec change:
openspec/changes/codebase-import-runtime-hardening/Scope
packages/specfact-project— shared import ignore policy,.specfact/.specfactignore, large-artifact warnings, dynamic ETA/progress, generator template packagingpackages/specfact-codebase— import command/runtime alignmentCapabilities
codebase-import-runtimebundle-packaged-resourcesParent Feature
Part of #234 — [Feature] Code Import Runtime Hardening