[1.0 T12] Package and release the complete 1.0 experience #188

Problem and outcome

Ship a coherent recommendation-first loop that preserves FluencyLoop strong principles, with compatibility and evidence of human benefit before release.

Interaction contract

Keep FluencyLoop. Proposed positioning: Stay fluent as people and agents evolve the product.

Use retained product reasoning automatically. Explain consequential choices at the right depth. Recommend a path. Continue within agreed intent. Ask when human judgment is needed. Update the shared model at natural boundaries.

The flagship goal/principles/precedents/tradeoffs reasoning is integrated into the existing design explanation at proportional depth. It is not a mandatory recital, proposal form, or new approval exchange. People must remain able to understand and challenge the design.

Scope

• Confirm version/positioning from T1 and T11 evidence. Update README/MANIFESTO around human fluency, delegated action, proportional explanation, and natural closure.
• Document the deliberate replacement of automatic blocking familiarity/understanding checks and support for requested guided learning. Ensure both distributions agree.
• Verify absent briefs, incomplete historical records, and advisory site warnings do not add implementation/delivery gates. Include no duplicated capture requirement.
• Run full cross-platform CI and both-host/legacy-project smoke sessions. Bump VERSION/manifests only at release and prepare a dev-to-main PR with observed evidence and forward recovery.

Acceptance criteria

• Shipped runtime, skills, site, and docs share the interaction contract and preserve the four standing principles.
• T1 pilot and T11 regression evidence support both design benefit and acceptable human attention cost.
• Release smoke tests include recommendation-and-continue, necessary human judgment, absent brief, and requested learning.
• Cross-platform CI, Node-optional checks, manifests, compatibility, and relevant site/browser checks are green.
• No partial transition reaches main; do not claim proven long-term fluency gains from immediate observations.

Validation

Follow RELEASING.md/CONTRIBUTING.md and review strong-principle conformance explicitly. Use complete CI and observed release smoke runs; promotion/tagging remain later release work, not actions in this planning update.

Starting points

RELEASING.md, CONTRIBUTING.md, README.md, MANIFESTO.md, CHANGELOG.md, plugins/fluencyloop/VERSION, manifests, .github/scripts/bump-version.sh

Constraints

• Target dev; main distributes releases. No runtime implementation occurs in the planning PR.
• T1 is an observed pilot using existing artifacts before new infrastructure. Use its evidence to retain, narrow, or defer later scope.
• Recommend and continue within authorized intent; ask with a recommendation only for consequential unresolved judgment. Batch independent questions, reuse settled answers, and wait for dependent work. Silence is not approval.
• Absent briefs, historical link gaps, stale prose, and unreviewed metadata alone are advisory. Do not require onboarding, cleanup, or retrospective approvals to work.
• Unknown familiarity is not fluency and does not automatically require a blocking probe/check. Support requested guided learning without quizzes; keep calibration/preferences private. T5 explicitly updates inherited pause rules.
• Capture rationale once, link mechanical views, record outcome deviations at natural closure, distill once at wrap-up, and reuse unchanged context.
• Preserve append-only history/provenance; Bash and PowerShell implement the same contract. Core remains Node-optional; no new database, hosted service, or vector search.

Dependencies and size

• Task: T12
• Relative size: M (not a calendar estimate)
• Depends on: T11: [1.0 T11] Evaluate fresh-session design behavior and dogfood developer/designer journeys #187
• Milestone: https://github.com/baokhang83/fluencyloop/milestone/3
• Plan: draft source
• Planning PR: docs: propose FluencyLoop 1.0 shared product direction and design #189